All of lore.kernel.org
 help / color / mirror / Atom feed
From: Matthew Wilcox <matthew@wil.cx>
To: kernel-janitors@vger.kernel.org
Subject: Re: [PATCH] Some grammatical and whitespace cleanups in init.h.
Date: Fri, 30 Nov 2007 21:19:10 +0000	[thread overview]
Message-ID: <20071130211910.GI2584@parisc-linux.org> (raw)
In-Reply-To: <alpine.LFD.0.9999.0711301424120.25301@localhost.localdomain>

On Fri, Nov 30, 2007 at 04:01:56PM -0500, Robert P. J. Day wrote:
> On Fri, 30 Nov 2007, Matthew Wilcox wrote:
> 
> > On Fri, Nov 30, 2007 at 02:24:57PM -0500, Robert P. J. Day wrote:
> > > -/* These macros are used to mark some functions or
> > > - * initialized data (doesn't apply to uninitialized data)
> > > - * as `initialization' functions. The kernel can take this
> > > - * as hint that the function is used only during the initialization
> > > - * phase and free up used memory resources after
> > > +/* These macros are used to mark functions and initialized
> > > + * data as 'initialization' objects, which tells the kernel that
> > > + * they are used only during the initialization phase and can be
> > > + * freed afterwards to recover memory.
> >
> > If you're going to get rid of 'some', then you need to change 'are' to
> > 'may be' or 'can be'.
> 
> i'm sorry, i don't see a problem here.  that replacement text looks
> perfectly unambiguous.  how do you think it might be misinterpreted?

It implies that all functions have to be marked as __init, which is
plainly not true.

-- 
Intel are signing my paycheques ... these opinions are still mine
"Bill, look, we understand that you're interested in selling us this
operating system, but compare it to ours.  We can't possibly take such
a retrograde step."

  parent reply	other threads:[~2007-11-30 21:19 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-30 19:24 [PATCH] Some grammatical and whitespace cleanups in init.h Robert P. J. Day
2007-11-30 19:42 ` Matthew Wilcox
2007-11-30 21:01 ` Robert P. J. Day
2007-11-30 21:19 ` Matthew Wilcox [this message]
2007-11-30 21:28 ` Robert P. J. Day

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=20071130211910.GI2584@parisc-linux.org \
    --to=matthew@wil.cx \
    --cc=kernel-janitors@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 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.