From: William Lee Irwin III <wli@holomorphy.com>
To: Paul Jackson <pj@sgi.com>
Cc: Andrew Morton <akpm@osdl.org>,
kaos@melbourne.sgi.com, joe.korty@ccur.com, tony.luck@intel.com,
linux-kernel@vger.kernel.org,
David Mosberger-Tang <davidm@hpl.hp.com>,
Christoph Hellwig <hch@infradead.org>,
jbarnes@sgi.com, Simon.Derr@bull.net
Subject: Re: [PATCH] new /proc/irq cpumask format; consolidate cpumask display and input code
Date: Fri, 28 Nov 2003 13:09:31 -0800 [thread overview]
Message-ID: <20031128210931.GZ8039@holomorphy.com> (raw)
In-Reply-To: <20031128125428.46ec7606.pj@sgi.com>
On Fri, Nov 28, 2003 at 12:54:28PM -0800, Paul Jackson wrote:
> I believe that Andrew Morton has accepted Bill's patch into
> his 2.6.0-test10-mm1 patch set as the "format_cpumask" patch.
> I hope that the following patch will replace Bill's patch.
> I look forward to Bill's feedback on this patch.
> The following patch carries Bill's work further:
> 1) It also consolidates the input side (write syscalls).
> 2) It adapts a new format, same on input and output.
> 3) The core routines work for any multi-word bitmask,
> not just cpumasks.
> 4) The core routines avoid overrunning their output
> buffers.
I like this a bit better than format_cpumask() since it's more
comprehensive. I don't believe you'll have a tough time selling
the format either, since it is easier to parse.
-- wli
prev parent reply other threads:[~2003-11-28 21:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-17 23:56 format_cpumask() Luck, Tony
2003-11-18 0:00 ` format_cpumask() William Lee Irwin III
2003-11-18 0:03 ` format_cpumask() William Lee Irwin III
[not found] ` <20031118002213.GA6272@tsunami.ccur.com>
2003-11-18 0:26 ` format_cpumask() William Lee Irwin III
2003-11-18 0:34 ` format_cpumask() Keith Owens
2003-11-18 0:56 ` format_cpumask() William Lee Irwin III
2003-11-28 20:54 ` [PATCH] new /proc/irq cpumask format; consolidate cpumask display and input code Paul Jackson
2003-11-28 21:09 ` William Lee Irwin III [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=20031128210931.GZ8039@holomorphy.com \
--to=wli@holomorphy.com \
--cc=Simon.Derr@bull.net \
--cc=akpm@osdl.org \
--cc=davidm@hpl.hp.com \
--cc=hch@infradead.org \
--cc=jbarnes@sgi.com \
--cc=joe.korty@ccur.com \
--cc=kaos@melbourne.sgi.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pj@sgi.com \
--cc=tony.luck@intel.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;
as well as URLs for NNTP newsgroup(s).