From: Damian Tometzki <damian.tometzki@icloud.com>
To: valdis.kletnieks@vt.edu, Pintu Kumar <pintu.ping@gmail.com>
Cc: linux-kernel@vger.kernel.org, kernelnewbies@kernelnewbies.org
Subject: Re: How to verify linux-next
Date: Fri, 29 Sep 2017 15:14:45 +0200 [thread overview]
Message-ID: <1506690885.1771.6.camel@icloud.com> (raw)
In-Reply-To: <159555.1506688878@turing-police.cc.vt.edu>
Hello,
Ubuntu 16.04 with current linux-next Kernel workson virtualbox 5.1.28
Host: Windows 10
Guest: Ubuntu 16.04
Best regards
Damian
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.
next prev parent reply other threads:[~2017-09-29 13:14 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-29 9:42 How to verify linux-next Pintu Kumar
2017-09-29 9:46 ` Pintu Kumar
2017-09-29 10:38 ` Pintu Kumar
2017-09-29 12:41 ` valdis.kletnieks
2017-09-29 13:05 ` Damian Tometzki
2017-09-29 13:14 ` Damian Tometzki [this message]
2017-09-29 14:26 ` Pintu Kumar
2017-09-29 15:45 ` valdis.kletnieks
2017-10-02 8:11 ` Kamil Konieczny
2017-10-02 11:04 ` valdis.kletnieks
2017-09-29 17:53 ` Pintu Kumar
2017-09-29 21:50 ` Theodore Ts'o
2017-09-30 3:58 ` Pintu Kumar
2017-09-30 5:25 ` Theodore Ts'o
2017-10-01 16:28 ` Pintu Kumar
2017-10-01 16:44 ` Damian Tometzki
2017-10-01 16:48 ` Randy Dunlap
2017-10-01 17:03 ` Mike Galbraith
2017-10-01 18:47 ` Pintu Kumar
2017-10-01 16:47 ` Theodore Ts'o
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1506690885.1771.6.camel@icloud.com \
--to=damian.tometzki@icloud.com \
--cc=kernelnewbies@kernelnewbies.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pintu.ping@gmail.com \
--cc=valdis.kletnieks@vt.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).