From: David Rientjes <rientjes@google.com>
To: liguang <lig.fnst@cn.fujitsu.com>
Cc: tglx@linutronix.de, hpa@zytor.com, pavel@ucw.cz, rjw@sisk.pl,
lv.zheng@intel.com, jarkko.sakkinen@intel.com,
dave@linux.vnet.ibm.com, linux-kernel@vger.kernel.org,
linux-acpi@vger.kernel.org, x86@kernel.org
Subject: Re: [rebased-again][PATCH 1/4] acpi: move x86/mm/srat.c to x86/kernel/acpi/srat.c
Date: Mon, 25 Feb 2013 14:51:30 -0800 (PST) [thread overview]
Message-ID: <alpine.DEB.2.02.1302251450160.4488@chino.kir.corp.google.com> (raw)
In-Reply-To: <1361759917-5195-2-git-send-email-lig.fnst@cn.fujitsu.com>
On Mon, 25 Feb 2013, liguang wrote:
> srat table should present only on acpi domain,
> seems mm/ is not the right place for it.
>
> Reviewed-by: Yasuaki Ishimatsu <isimatu.yasuaki@jp.fujitsu.com>
> Signed-off-by: liguang <lig.fnst@cn.fujitsu.com>
You're still missing 01a178a94e8e ("acpi, memory-hotplug: support getting
hotplug info from SRAT") that was merged at the end of last week. Instead
of continuing to rebase perhaps it would be better at this point to ask
the x86 maintainers to just do the patch for you?
next prev parent reply other threads:[~2013-02-25 22:51 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-25 2:38 [rebased-again][PATCH 0/4] acpi: do some changes for numa info liguang
2013-02-25 2:38 ` [rebased-again][PATCH 1/4] acpi: move x86/mm/srat.c to x86/kernel/acpi/srat.c liguang
2013-02-25 22:51 ` David Rientjes [this message]
2013-02-26 1:01 ` li guang
2013-02-25 2:38 ` [rebased-again][PATCH 2/4] numa: avoid export acpi_numa variable liguang
2013-02-25 2:38 ` [rebased-again][PATCH 3/4] acpi: add clock_domain field to acpi_srat_cpu_affinity liguang
2013-02-25 2:38 ` [rebased-again][PATCH 4/4] remove include asm/acpi.h in process_driver.c liguang
2013-03-04 1:21 ` [rebased-again][PATCH 0/4] acpi: do some changes for numa info li guang
2013-04-09 0:23 ` li guang
2013-05-23 0:25 ` li guang
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=alpine.DEB.2.02.1302251450160.4488@chino.kir.corp.google.com \
--to=rientjes@google.com \
--cc=dave@linux.vnet.ibm.com \
--cc=hpa@zytor.com \
--cc=jarkko.sakkinen@intel.com \
--cc=lig.fnst@cn.fujitsu.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lv.zheng@intel.com \
--cc=pavel@ucw.cz \
--cc=rjw@sisk.pl \
--cc=tglx@linutronix.de \
--cc=x86@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
all inboxes | Powered by JetHome®