From: Andi Kleen <andi@firstfloor.org>
To: "Cihula, Joseph" <joseph.cihula@intel.com>
Cc: <linux-kernel@vger.kernel.org>,
"Wang, Shane" <shane.wang@intel.com>,
"Wei, Gang" <gang.wei@intel.com>,
"Van De Ven, Arjan" <arjan.van.de.ven@intel.com>,
"Mallick, Asit K" <asit.k.mallick@intel.com>,
"Nakajima, Jun" <jun.nakajima@intel.com>,
"Chris Wright" <chrisw@redhat.com>,
"Jan Beulich" <jbeulich@novell.com>, <mingo@elte.hu>,
<tytso@mit.edu>
Subject: Re: [RFC][PATCH 1/3] TXT: ACPI AddressRangeUnusuable support
Date: Wed, 08 Oct 2008 02:54:16 +0200 [thread overview]
Message-ID: <87iqs3lxdz.fsf@basil.nowhere.org> (raw)
In-Reply-To: <D936D925018D154694D8A362EEB0892005AC105D@orsmsx416.amr.corp.intel.com> (Joseph Cihula's message of "Tue, 7 Oct 2008 13:34:47 -0700")
"Cihula, Joseph" <joseph.cihula@intel.com> writes:
> +#define E820_UNUSABLE 5
>
> /* reserved RAM used by kernel itself */
> #define E820_RESERVED_KERN 128
>
> From: <akpm@linux-foundation.org>
Something got corrupted? Your patch contains a mailbox with another
version of the patch.
> Subject: - acpi-add-support-for-addressrangeunusuable-acpi-memory-type.patch removed from -mm tree
> To: "Cihula, Joseph" <joseph.cihula@intel.com>,
> <andi@firstfloor.org>,
> "Wei, Gang" <gang.wei@intel.com>,
> <mingo@elte.hu>,
> "Wang, Shane" <shane.wang@intel.com>,
> <tglx@linutronix.de>,
> <mm-commits@vger.kernel.org>
> Date: Tue, 26 Aug 2008 11:44:49 -0700
>
>
> The patch titled
> acpi: add support for AddressRangeUnusuable ACPI memory type
> has been removed from the -mm tree. Its filename was
> acpi-add-support-for-addressrangeunusuable-acpi-memory-type.patch
-Andi
--
ak@linux.intel.com
next prev parent reply other threads:[~2008-10-08 0:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-07 20:34 [RFC][PATCH 1/3] TXT: ACPI AddressRangeUnusuable support Cihula, Joseph
2008-10-08 0:54 ` Andi Kleen [this message]
2008-10-08 4:32 ` Cihula, Joseph
-- strict thread matches above, loose matches on Subject: below --
2008-10-07 22:57 Joseph Cihula
2008-10-07 23:40 ` Joseph Cihula
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=87iqs3lxdz.fsf@basil.nowhere.org \
--to=andi@firstfloor.org \
--cc=arjan.van.de.ven@intel.com \
--cc=asit.k.mallick@intel.com \
--cc=chrisw@redhat.com \
--cc=gang.wei@intel.com \
--cc=jbeulich@novell.com \
--cc=joseph.cihula@intel.com \
--cc=jun.nakajima@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=shane.wang@intel.com \
--cc=tytso@mit.edu \
/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