Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1742148
| From | Damian Tometzki <damian.tometzki@icloud.com> |
|---|---|
| Newsgroups | linux.kernel |
| Subject | Re: How to verify linux-next |
| Date | 2017-09-29 16:10 +0200 |
| Message-ID | <uv49l-7bh-41@gated-at.bofh.it> (permalink) |
| References | <uv05H-4tr-3@gated-at.bofh.it> <uv05I-4tr-5@gated-at.bofh.it> <uv0S5-4Yx-9@gated-at.bofh.it> <uv33A-6hF-17@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
Hello, i can tell you ubuntu 16.04 works under virtualbox 5.1.28 with the current linux-next kernel My maschine: Host: Windows 10 Guest: Ubuntu 16.04 Am Freitag, den 29.09.2017, 08:41 -0400 schrieb valdis.kletnieks@vt.edu: > On Fri, 29 Sep 2017 16:08:07 +0530, Pintu Kumar said: > > > > > I have a general question. > > How do we normally verify linux-next tree? > The same exact way you "verify" any other Linux kernel, for whatever > definition of "verify" you plan to use. > > > > > 1) For Oracle virtual box 5.1.26 with ubuntu-32 bit, the linux-next > > kernel is not booting. > Does an Ubuntu kernel boot correctly under VirtualBox? If not, fix > that issue first. Also, "is not booting" isn't detailed enough for > anybody > to make even a guess as to what's wrong. > > Also, note that 5.1.28 is out.
Back to linux.kernel | Previous | Next — Previous in thread | Find similar | Unroll thread
How to verify linux-next Pintu Kumar <pintu.ping@gmail.com> - 2017-09-29 11:50 +0200
Re: How to verify linux-next Pintu Kumar <pintu.ping@gmail.com> - 2017-09-29 11:50 +0200
Re: How to verify linux-next Pintu Kumar <pintu.ping@gmail.com> - 2017-09-29 12:40 +0200
Re: How to verify linux-next valdis.kletnieks@vt.edu - 2017-09-29 15:00 +0200
Re: How to verify linux-next Damian Tometzki <damian.tometzki@icloud.com> - 2017-09-29 15:20 +0200
Re: How to verify linux-next Pintu Kumar <pintu.ping@gmail.com> - 2017-09-29 16:30 +0200
Re: How to verify linux-next valdis.kletnieks@vt.edu - 2017-09-29 17:50 +0200
Re: How to verify linux-next Kamil Konieczny <k.konieczny@partner.samsung.com> - 2017-10-02 10:20 +0200
Re: How to verify linux-next valdis.kletnieks@vt.edu - 2017-10-02 13:10 +0200
Re: How to verify linux-next Pintu Kumar <pintu.ping@gmail.com> - 2017-09-29 20:00 +0200
Re: How to verify linux-next Theodore Ts'o <tytso@mit.edu> - 2017-09-30 00:00 +0200
Re: How to verify linux-next Pintu Kumar <pintu.ping@gmail.com> - 2017-09-30 06:00 +0200
Re: How to verify linux-next Theodore Ts'o <tytso@mit.edu> - 2017-09-30 07:30 +0200
Re: How to verify linux-next Pintu Kumar <pintu.ping@gmail.com> - 2017-10-01 18:30 +0200
Re: How to verify linux-next Damian Tometzki <damian.tometzki@icloud.com> - 2017-10-01 18:50 +0200
Re: How to verify linux-next Randy Dunlap <rdunlap@infradead.org> - 2017-10-01 18:50 +0200
Re: How to verify linux-next Mike Galbraith <efault@gmx.de> - 2017-10-01 19:10 +0200
Re: How to verify linux-next Pintu Kumar <pintu.ping@gmail.com> - 2017-10-01 20:50 +0200
Re: How to verify linux-next Theodore Ts'o <tytso@mit.edu> - 2017-10-01 18:50 +0200
Re: How to verify linux-next Damian Tometzki <damian.tometzki@icloud.com> - 2017-09-29 16:10 +0200
csiph-web