public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: Alexey Dobriyan <adobriyan@gmail.com>
Cc: Paul Jackson <pj@sgi.com>,
	akpm@linuxfoundation.org, linux-kernel@vger.kernel.org,
	Mike Travis <travis@sgi.com>
Subject: Re: [PATCH 2/2] cpuset: use seq_cpumask(), seq_nodemask()
Date: Mon, 4 Aug 2008 16:41:01 -0700	[thread overview]
Message-ID: <20080804164101.51190a8b.akpm@linux-foundation.org> (raw)
In-Reply-To: <20080802142838.GA338@martell.zuzino.mipt.ru>

On Sat, 2 Aug 2008 18:28:38 +0400 Alexey Dobriyan <adobriyan@gmail.com> wrote:

> On Sat, Aug 02, 2008 at 09:05:42AM -0500, Paul Jackson wrote:
> > Alexey wrote:
> > > Folks might want to boot with NR_CPUS=4096 and see what happens,
> > > m->count games don't look promising. :-)
> > 
> > That comment is rather heavily dependent on the context of both:
> >  1) the previous patch comment, and
> >  2) booting and seeing.
> > 
> > Could you rewrite it, so that it doesn't depend on such context,
> > and can be read and understood, by itself?

I agree with Paul.  That changelog was useless, sorry.

> That's just a reminder to cpuset people whether /proc/*/status broken or
> not. Can be safely deleted. :-)

Deleting the changelog won't make it clearer (unlike some changelogs
which I've seen ;))

Please send a usable changleog for this patch, thanks.

      parent reply	other threads:[~2008-08-04 23:41 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-02 11:31 [PATCH 2/2] cpuset: use seq_cpumask(), seq_nodemask() Alexey Dobriyan
2008-08-02 14:05 ` Paul Jackson
2008-08-02 14:28   ` Alexey Dobriyan
2008-08-02 16:53     ` Paul Jackson
2008-08-04 23:41     ` Andrew Morton [this message]

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=20080804164101.51190a8b.akpm@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=adobriyan@gmail.com \
    --cc=akpm@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pj@sgi.com \
    --cc=travis@sgi.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