From: valdis.kletnieks@vt.edu
To: 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 08:41:18 -0400 [thread overview]
Message-ID: <159555.1506688878@turing-police.cc.vt.edu> (raw)
In-Reply-To: <CAOuPNLgFUgo0Cbbfu_96R3FHUL5VRnZq+-FMYJQ8XB8NLS_Djg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 553 bytes --]
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.
[-- Attachment #2: Type: application/pgp-signature, Size: 486 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: valdis.kletnieks@vt.edu (valdis.kletnieks at vt.edu)
To: kernelnewbies@lists.kernelnewbies.org
Subject: How to verify linux-next
Date: Fri, 29 Sep 2017 08:41:18 -0400 [thread overview]
Message-ID: <159555.1506688878@turing-police.cc.vt.edu> (raw)
In-Reply-To: <CAOuPNLgFUgo0Cbbfu_96R3FHUL5VRnZq+-FMYJQ8XB8NLS_Djg@mail.gmail.com>
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 part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 486 bytes
Desc: not available
Url : http://lists.kernelnewbies.org/pipermail/kernelnewbies/attachments/20170929/73b70e79/attachment.bin
next prev parent reply other threads:[~2017-09-29 12:56 UTC|newest]
Thread overview: 39+ 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 9:46 ` Pintu Kumar
2017-09-29 10:38 ` Pintu Kumar
2017-09-29 10:38 ` Pintu Kumar
2017-09-29 12:41 ` valdis.kletnieks [this message]
2017-09-29 12:41 ` valdis.kletnieks at vt.edu
2017-09-29 13:05 ` Damian Tometzki
2017-09-29 13:05 ` Damian Tometzki
2017-09-29 13:14 ` Damian Tometzki
2017-09-29 13:14 ` Damian Tometzki
2017-09-29 14:26 ` Pintu Kumar
2017-09-29 14:26 ` Pintu Kumar
2017-09-29 15:45 ` valdis.kletnieks
2017-09-29 15:45 ` valdis.kletnieks at vt.edu
2017-10-02 8:11 ` Kamil Konieczny
2017-10-02 8:11 ` Kamil Konieczny
2017-10-02 11:04 ` valdis.kletnieks
2017-10-02 11:04 ` valdis.kletnieks at vt.edu
2017-09-29 17:53 ` Pintu Kumar
2017-09-29 17:53 ` Pintu Kumar
2017-09-29 21:50 ` Theodore Ts'o
2017-09-29 21:50 ` Theodore Ts'o
2017-09-30 3:58 ` Pintu Kumar
2017-09-30 3:58 ` Pintu Kumar
2017-09-30 5:25 ` Theodore Ts'o
2017-09-30 5:25 ` Theodore Ts'o
2017-10-01 16:28 ` Pintu Kumar
2017-10-01 16:28 ` Pintu Kumar
2017-10-01 16:44 ` Damian Tometzki
2017-10-01 16:44 ` Damian Tometzki
2017-10-01 16:48 ` Randy Dunlap
2017-10-01 16:48 ` Randy Dunlap
2017-10-01 17:03 ` Mike Galbraith
2017-10-01 17:03 ` Mike Galbraith
2017-10-01 18:47 ` Pintu Kumar
2017-10-01 18:47 ` Pintu Kumar
2017-10-01 16:47 ` Theodore Ts'o
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=159555.1506688878@turing-police.cc.vt.edu \
--to=valdis.kletnieks@vt.edu \
--cc=kernelnewbies@kernelnewbies.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pintu.ping@gmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.