From: Stefan Richter <stefanr@s5r6.in-berlin.de>
To: Arjan van de Ven <arjan@infradead.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Miles Lane <miles.lane@gmail.com>,
LKML <linux-kernel@vger.kernel.org>,
Nishanth Aravamudan <nacc@us.ibm.com>,
Adam Litke <agl@us.ibm.com>,
David Gibson <david@gibson.dropbear.id.au>
Subject: Re: 2.6.24-git20 -- BUG: sleeping function called from invalid context at include/asm/uaccess_32.h:449
Date: Sun, 10 Feb 2008 11:44:48 +0100 [thread overview]
Message-ID: <47AED5A0.8040003@s5r6.in-berlin.de> (raw)
In-Reply-To: <20080209163812.704cf282@laptopd505.fenrus.org>
Arjan van de Ven wrote:
> On Sat, 9 Feb 2008 16:26:43 -0800
> Andrew Morton <akpm@linux-foundation.org> wrote:
>> Guys, how often mut it be said? PLEASE always test all code with all
>> kernel deubg options enabled.
>
> maybe we should make a CONFIG_KERNEL_DEVELOPER option that SELECTs the
> various options that really should be on.
>
> If there is a chance of reasonable agreement on what those options are I'll cook
> up a patch...
There are a few in Documentation/SubmitChecklist items 12 and 15.
> (but I don't want to get bogged down in a 500 mail flamewar about
> CONFIG_FOO_BAR being right for this or not...)
You can be rather sure that there will be at least... questions and
concerns... ;-)
Anyway, the root problem is that developers and integrators don't take
time to follow the rules in SubmitChecklist. (I know that I still have
ways to go to improve my own processes in that regard.) A Kconfig
switch may raise awareness of SubmitChecklist a little bit, but I'm
afraid it is not awareness what's the issue here.
--
Stefan Richter
-=====-==--- --=- -=-=-
http://arcgraph.de/sr/
next prev parent reply other threads:[~2008-02-10 10:46 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-09 19:03 Miles Lane
2008-02-10 0:26 ` Andrew Morton
2008-02-10 0:38 ` Arjan van de Ven
2008-02-10 10:44 ` Stefan Richter [this message]
2008-02-10 21:26 ` Nishanth Aravamudan
2008-02-10 21:25 ` Nishanth Aravamudan
2008-02-11 22:28 ` Nishanth Aravamudan
2008-02-12 3:57 ` Miles Lane
2008-02-12 4:17 ` Miles Lane
2008-02-12 5:16 ` Nishanth Aravamudan
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=47AED5A0.8040003@s5r6.in-berlin.de \
--to=stefanr@s5r6.in-berlin.de \
--cc=agl@us.ibm.com \
--cc=akpm@linux-foundation.org \
--cc=arjan@infradead.org \
--cc=david@gibson.dropbear.id.au \
--cc=linux-kernel@vger.kernel.org \
--cc=miles.lane@gmail.com \
--cc=nacc@us.ibm.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®