From: Andrew Morton <akpm@linux-foundation.org>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: Alexey Dobriyan <adobriyan@gmail.com>,
davem@davemloft.net, mingo@elte.hu, nhorman@tuxdriver.com,
simon@fire.lp0.eu, linux-kernel@vger.kernel.org
Subject: Re: BUG: unable to handle kernel NULL pointer dereference at 000000000000000e (reset_prng_context)
Date: Tue, 15 Jul 2008 21:25:49 -0700 [thread overview]
Message-ID: <20080715212549.1c41c1d0.akpm@linux-foundation.org> (raw)
In-Reply-To: <20080716040701.GA12570@gondor.apana.org.au>
On Wed, 16 Jul 2008 12:07:01 +0800 Herbert Xu <herbert@gondor.apana.org.au> wrote:
> On Tue, Jul 15, 2008 at 03:11:10PM -0700, Andrew Morton wrote:
> >
> > Except that such a high density of coding-style errors is an indication
> > that the code was not closely and critically reviewed by an experienced
> > kernel developer.
> >
> > > Every damn single warning in this case is about whitespace or 80 column limit.
> > >
> > > Every damn single one!
>
> Indeed, I apologise for reviewing the code on a monitor that is wider
> than yours. If only we could make sure that all Linux developers
> used smaller monitors then the code quality would surely improve!
>
Remaining within 80 cols is a big deal indeed for those who choose to
use, or who are forced to use 80-col displays. Try resizing to 70 cols
for a while, see how you get on.
And that's the point: the utility to you (and me) of using >80 cols is
much less than the loss of utility to those who are stuck with 80 cols.
That's why we have a standard.
me, I'd be perfectly happy with upping that standard to 96 cols but I
seem unable to get anyone else to chew on that bait so shrug. But for the
above reasons we _do_ need to have a standard and to stick to it.
(I mean it - try the 70 col experiment!)
next prev parent reply other threads:[~2008-07-16 4:27 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-14 23:25 BUG: unable to handle kernel NULL pointer dereference at 000000000000000e (reset_prng_context) Simon Arlott
2008-07-15 2:04 ` Neil Horman
2008-07-15 11:33 ` Ingo Molnar
2008-07-15 11:49 ` Ingo Molnar
2008-07-15 11:51 ` Ingo Molnar
2008-07-15 14:21 ` Neil Horman
2008-07-15 20:44 ` David Miller
2008-07-15 21:49 ` Alexey Dobriyan
2008-07-15 22:11 ` Andrew Morton
2008-07-15 22:36 ` Alexey Dobriyan
2008-07-16 0:04 ` Neil Horman
2008-07-16 2:08 ` Herbert Xu
2008-07-16 4:07 ` Herbert Xu
2008-07-16 4:25 ` Andrew Morton [this message]
2008-07-16 4:33 ` Herbert Xu
2008-07-16 4:51 ` Andrew Morton
2008-07-16 5:34 ` Herbert Xu
2008-07-16 6:17 ` Andrew Morton
2008-07-16 6:35 ` Herbert Xu
2008-07-16 16:57 ` Joe Perches
2008-07-18 22:16 ` Ingo Molnar
2008-07-15 2:16 ` Neil Horman
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=20080715212549.1c41c1d0.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=adobriyan@gmail.com \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=nhorman@tuxdriver.com \
--cc=simon@fire.lp0.eu \
/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