From: David Mosberger <davidm@napali.hpl.hp.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [PATCH] initialize bootmem maps in reverse order
Date: Fri, 19 Dec 2003 23:07:29 +0000 [thread overview]
Message-ID: <marc-linux-ia64-107187526421837@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-107151544512148@msgid-missing>
>>>>> On Wed, 17 Dec 2003 07:12:39 -0800, jbarnes@sgi.com (Jesse Barnes) said:
Jesse> Great! Fixed it first try! :) David, does this patch look ok
Jesse> for 2.6.1?
The patch looks fine to me, except for the weird whitespace in front of
the declration of "cpu_data" (not introduced by your patch, but while
you're working in that neighborhood, why not fix it?).
Also, please include a brief description of what the patch does (for
bk changelog). You probably have done that with the original patch,
but I don't have that anymore.
Thanks,
--david
next prev parent reply other threads:[~2003-12-19 23:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-15 18:59 [PATCH] initialize bootmem maps in reverse order Jesse Barnes
2003-12-17 8:06 ` Xavier Bru
2003-12-17 15:12 ` Jesse Barnes
2003-12-19 23:07 ` David Mosberger [this message]
2003-12-19 23:20 ` Jesse Barnes
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=marc-linux-ia64-107187526421837@msgid-missing \
--to=davidm@napali.hpl.hp.com \
--cc=linux-ia64@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox