linux-kbuild.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Piotr Hosowicz <piotr@hosowicz.com>
To: linux-kbuild@vger.kernel.org
Subject: Maybe my frequent kernel building could be of some help to the community? And how to build?
Date: Tue, 16 Mar 2010 20:02:41 +0100	[thread overview]
Message-ID: <4B9FD5D1.8040203@example.com> (raw)

Hello,

I own quite strong PC, 4 core Pentium. I recently started to build my 
kernel frequently, whenever I see a new patch on kernel.org I build 
again. Bothers me that I do it only for doing it. Maybe it could be of 
some help to the community? And if so, what would be more appreciated - 
linux-next patched kernel or gitN patched kernel? And how should I 
configure the kernel for this purpose? I am afraid of putting all the 
options on, yesterday I tried to put everything on as a module plus I 
tinkered with some other options that seemed innocent. The kernel was 
built but could not boot, saying that there was a problem with the root 
device, it could not recoginze /dev/sda2, which is my correct root 
device. I did not investigate much and reverted to working kernel.

Thanks in advance for your remarks.

Regards,

Piotr Hosowicz

-- 
"Chcemy waszego dobra!" - powiedział lider
socjaldemokratów. Zaniepokojeni obywatele
zaczeli ukrywać swoje dobra w bezpiecznych
miejscach.
NP:  -

             reply	other threads:[~2010-03-16 19:09 UTC|newest]

Thread overview: 47+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-16 19:02 Piotr Hosowicz [this message]
2010-03-16 19:24 ` Maybe my frequent kernel building could be of some help to the community? And how to build? Randy Dunlap
2010-03-16 19:33   ` Piotr Hosowicz
2010-03-16 19:42     ` Randy Dunlap
2010-03-17  3:24   ` Piotr Hosowicz
2010-03-17 15:07     ` Randy Dunlap
     [not found]       ` <4BA0F8DE.1050006@example.com>
2010-03-17 15:54         ` Randy Dunlap
2010-03-17 16:03           ` Piotr Hosowicz
2010-03-17 17:49           ` Piotr Hosowicz
2010-03-17 17:53             ` Randy Dunlap
2010-03-18 15:40   ` Randy Dunlap
2010-03-22  3:31     ` Piotr Hosowicz
2010-03-22  3:48       ` Randy Dunlap
2010-03-22 12:42         ` Piotr Hosowicz
2010-03-22 12:53           ` Piotr Hosowicz
2010-03-24  1:12             ` Piotr Hosowicz
2010-03-24 21:43               ` Randy Dunlap
2010-03-25 11:38                 ` Piotr Hosowicz
2010-03-25 17:29     ` Randy Dunlap
2010-03-25 17:37       ` Piotr Hosowicz
2010-03-25 17:40         ` Randy Dunlap
2010-03-25 17:48           ` Piotr Hosowicz
2010-03-25 17:54             ` Randy Dunlap
2010-03-25 18:35               ` Piotr Hosowicz
2010-03-25 22:04                 ` Randy Dunlap
2010-03-25 22:15                   ` Piotr Hosowicz
2010-03-26 16:46                     ` Piotr Hosowicz
2010-03-27 16:37                       ` Piotr Hosowicz
2010-03-27 16:39                         ` Piotr Hosowicz
2010-04-01 16:02       ` Randy Dunlap
2010-04-01 17:24         ` Piotr Hosowicz
2010-04-01 17:44           ` Piotr Hosowicz
2010-03-29 20:16   ` Is root kernel parameter expected to be the first one or something? Piotr Hosowicz
2010-03-29 20:38     ` Randy Dunlap
2010-03-29 20:41       ` Piotr Hosowicz
2010-03-29 21:33         ` Randy Dunlap
2010-03-29 22:32           ` Piotr Hosowicz
2010-03-29 22:39             ` Randy Dunlap
2010-03-29 22:44               ` Piotr Hosowicz
2010-03-29 22:48                 ` Randy Dunlap
2010-03-29 22:55                   ` Piotr Hosowicz
2010-03-29 23:06                     ` Randy Dunlap
2010-03-29 23:44                       ` Piotr Hosowicz
2010-03-30 16:37                   ` Piotr Hosowicz
2010-03-30 18:03                     ` Piotr Hosowicz
2010-03-30 19:00                       ` Piotr Hosowicz
2010-03-31  9:15                         ` Piotr Hosowicz

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=4B9FD5D1.8040203@example.com \
    --to=piotr@hosowicz.com \
    --cc=linux-kbuild@vger.kernel.org \
    /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).