From: Andrew Morton <akpm@osdl.org>
To: Nick Piggin <piggin@cyberone.com.au>
Cc: mbligh@aracnet.com, linux-kernel@vger.kernel.org,
nevdull@us.ibm.com, dvhart@us.ibm.com
Subject: Re: [PATCH] clarify find_busiest_group
Date: Thu, 22 Jan 2004 23:02:37 -0800 [thread overview]
Message-ID: <20040122230237.252c4dbe.akpm@osdl.org> (raw)
In-Reply-To: <4010C2BF.7090806@cyberone.com.au>
Nick Piggin <piggin@cyberone.com.au> wrote:
>
> Andrew would you like me to take small changes like this and
> feed them to you, or are you happy enough to pick them up?
I scooped that one up. The main outstanding thing is Rusty's largeish
patch.
<looks>
Time for -mm2, methinks.
next prev parent reply other threads:[~2004-01-23 7:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-23 6:31 [PATCH] clarify find_busiest_group Martin J. Bligh
2004-01-23 6:44 ` Nick Piggin
2004-01-23 7:02 ` Andrew Morton [this message]
2004-01-23 12:43 ` vts have stopped working here Ed Tomlinson
2004-01-23 13:05 ` Vojtech Pavlik
2004-01-23 15:05 ` Ed Tomlinson
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=20040122230237.252c4dbe.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=dvhart@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mbligh@aracnet.com \
--cc=nevdull@us.ibm.com \
--cc=piggin@cyberone.com.au \
/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