From: Ingo Molnar <mingo@elte.hu>
To: Alok Kataria <akataria@vmware.com>
Cc: "Brown, Len" <len.brown@intel.com>,
Andrew Morton <akpm@linux-foundation.org>,
linux-acpi@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
Yinghai Lu <yhlu.kernel@gmail.com>
Subject: Re: [PATCH 1/2] cleanup e820_setup_gap
Date: Fri, 20 Jun 2008 17:32:20 +0200 [thread overview]
Message-ID: <20080620153220.GD17373@elte.hu> (raw)
In-Reply-To: <1213916250.27983.35.camel@promb-2n-dhcp368.eng.vmware.com>
* Alok Kataria <akataria@vmware.com> wrote:
> This is a preparatory patch for the next patch in series. Moves some
> code from e820_setup_gap to a new function e820_search_gap. This
> function will be used by the next patch in the series.
>
> Signed-off-by: Alok N Kataria <akataria@vmware.com>
>
> Index: linux-2.6/arch/x86/kernel/e820_64.c
> ===================================================================
> --- linux-2.6.orig/arch/x86/kernel/e820_64.c 2008-06-12 10:42:22.000000000 -0700
> +++ linux-2.6/arch/x86/kernel/e820_64.c 2008-06-13 14:05:18.000000000 -0700
> @@ -872,26 +872,20 @@
note that this code has significantly changed in x86-next (it has been
fixed, extended, cleaned up and unified). You can find the latest
patches in tip/master at:
http://people.redhat.com/mingo/tip.git/README
tip/master contains the integration of all changes in this area.
We could apply and test your change in tip/x86 as well, as it seems
standalone and independent of ACPI - so that when the acpi change shows
up in linux-next there's a e820_search_gap() function available.
Ingo
next prev parent reply other threads:[~2008-06-20 15:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-19 22:57 [PATCH 1/2] cleanup e820_setup_gap Alok Kataria
2008-06-20 15:32 ` Ingo Molnar [this message]
2008-06-20 19:38 ` Alok Kataria
2008-06-20 19:50 ` Yinghai Lu
2008-06-20 20:28 ` Alok Kataria
2008-06-24 12:08 ` Ingo Molnar
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=20080620153220.GD17373@elte.hu \
--to=mingo@elte.hu \
--cc=akataria@vmware.com \
--cc=akpm@linux-foundation.org \
--cc=len.brown@intel.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=yhlu.kernel@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.