From: Olof Johansson <olof@lixom.net>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: linuxppc-dev list <linuxppc-dev@ozlabs.org>,
Paul Mackerras <paulus@samba.org>
Subject: Re: [PATCH] powerpc: Fix demotion of segments to 4K pages
Date: Sun, 28 Oct 2007 22:06:48 -0500 [thread overview]
Message-ID: <20071029030648.GA14199@lixom.net> (raw)
In-Reply-To: <1193623229.9928.2.camel@pasglop>
On Mon, Oct 29, 2007 at 01:00:29PM +1100, Benjamin Herrenschmidt wrote:
> On Sun, 2007-10-28 at 20:50 -0500, Olof Johansson wrote:
> > Hi Ben,
> >
> > On Mon, Oct 29, 2007 at 12:05:18PM +1100, Benjamin Herrenschmidt wrote:
> > > @@ -887,6 +886,9 @@ void hash_preload(struct mm_struct *mm,
> > > local_irq_restore(flags);
> > > }
> > >
> > > +/* WARNING: This is called from hash_low_64.S, if you change this prototype,
> > > + * do not forget to update the assembly call site !
> > > + */
> >
> > Since we're already policing whitespace on this list today: We're normally
> > not using spaces before exclamation marks.
>
> And I don't care, I will continue adding them because the opposite is
> fugly :-)
Yeah , I know what you mean . This looks so much more natural .
> There is a limit to what I accept from the style police, it's not like
> Linux has to look like it's written by a single person either.
Good one ! That one goes to the bookmark list . :-)
I agree though , whitespace policing tends to be counter-productive ,
together with (minor) grammar and spelling errors in comments . Still,
people love to point them out so I figured I would do it too .
- Olof
next prev parent reply other threads:[~2007-10-29 2:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-29 1:05 [PATCH] powerpc: Fix demotion of segments to 4K pages Benjamin Herrenschmidt
2007-10-29 1:50 ` Olof Johansson
2007-10-29 2:00 ` Benjamin Herrenschmidt
2007-10-29 3:06 ` Olof Johansson [this message]
2007-10-29 3:24 ` Benjamin Herrenschmidt
2007-10-29 8:32 ` Geert Uytterhoeven
2007-10-29 2:18 ` Stephen Rothwell
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=20071029030648.GA14199@lixom.net \
--to=olof@lixom.net \
--cc=benh@kernel.crashing.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=paulus@samba.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 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.