From: Andi Kleen <ak@suse.de>
To: Arjan van de Ven <arjan@linux.intel.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [patch 1 of 4] Rename e820_map to e820_any_map to reflect its behavior better
Date: Sat, 25 Mar 2006 17:50:10 +0100 [thread overview]
Message-ID: <200603251750.10444.ak@suse.de> (raw)
In-Reply-To: <1143303796.2898.6.camel@laptopd505.fenrus.org>
On Saturday 25 March 2006 17:23, Arjan van de Ven wrote:
> Rename e820_mapped to e820_any_mapped since it tests if any part
> of the range is mapped according to the type. Later steps will introduce
> e820_all_mapped which will check if the entire range is mapped with the type.
> Both have their merit.
I merged it after fixing it all up. There were rejects. Merged the i386
changes with the x86-64 changes. And removed the bogus hunk in the MCFG
patch. Also some cosmetic changes to make the lines < 80 chars
Thanks,
-Andi
prev parent reply other threads:[~2006-03-25 16:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-25 16:23 [patch 1 of 4] Rename e820_map to e820_any_map to reflect its behavior better Arjan van de Ven
2006-03-25 16:24 ` [patch 2 of 4] Introduce e820_all_mapped Arjan van de Ven
2006-03-25 16:24 ` [patch 3 of 4] MCFG sanity check Arjan van de Ven
2006-03-25 16:25 ` [patch 4 of 4] i386 version of the changes Arjan van de Ven
2006-03-25 16:50 ` Andi Kleen [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=200603251750.10444.ak@suse.de \
--to=ak@suse.de \
--cc=arjan@linux.intel.com \
--cc=linux-kernel@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