From: li guang <lig.fnst@cn.fujitsu.com>
To: tglx@linutronix.de
Cc: 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 0/4] acpi: do some changes for numa info
Date: Tue, 09 Apr 2013 08:23:09 +0800 [thread overview]
Message-ID: <1365466989.9553.1.camel@liguang.fnst.cn.fujitsu.com> (raw)
In-Reply-To: <1362360079.19928.1.camel@liguang.fnst.cn.fujitsu.com>
ping ...
在 2013-03-04一的 09:21 +0800，li guang写道：
> Hi, Thomas, Peter, Ingo
>
> can you help to merge these 4 patches?
> or do you have any other comments?
>
>
> 在 2013-02-25一的 10:38 +0800，liguang写道：
> > just do some trivial changes to make acpi's numa info
> > operation more cleaner.
> >
> > ChangeLog
> >
> > v3->v4
> > 1.fix srat_disabled function
> > spotted by Yasuaki Ishimatsu <isimatu.yasuaki@jp.fujitsu.com>
> >
> > v2->v3
> > 1. rebase on linux-next
> > 2. bring back lost Makefile changes
> > spotted by David Rientjes <rientjes@google.com>
> > spotted by Yasuaki Ishimatsu <isimatu.yasuaki@jp.fujitsu.com>
> >
> > v1->v2
> > 1. fix-up several coding issues
> > 2. finish srat.c change
> > spotted by David Rientjes <rientjes@google.com>
> >
> > Li Guang (4)
> > acpi: move x86/mm/srat.c to x86/kernel/acpi/srat.c
> > numa: avoid export acpi_numa variable
> > acpi: add clock_domain field to acpi_srat_cpu_affinity
> > remove include asm/acpi.h in process_driver.c
> >
> > arch/x86/include/asm/acpi.h | 2 +-
> > arch/x86/kernel/acpi/Makefile | 1 +
> > arch/x86/kernel/acpi/srat.c | 299 +++++++++++++++++++++++++++++++++++++++++
> > arch/x86/mm/Makefile | 1 -
> > arch/x86/mm/numa.c | 2 +-
> > arch/x86/mm/srat.c | 278 -----------------------------------------
> > arch/x86/xen/enlighten.c | 2 +-
> > drivers/acpi/processor_driver.c | 1 -
> > include/acpi/actbl1.h | 2 +-
> > 9 files changed, 296 insertions(+), 292 deletions(-)
> > create mode 100644 arch/x86/kernel/acpi/srat.c
> > delete mode 100644 arch/x86/mm/srat.c
> >
> > --
> > To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> > the body of a message to majordomo@vger.kernel.org
> > More majordomo info at http://vger.kernel.org/majordomo-info.html
> > Please read the FAQ at http://www.tux.org/lkml/
>
next prev parent reply other threads:[~2013-04-09 0:24 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-25 2:38 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
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 [this message]
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=1365466989.9553.1.camel@liguang.fnst.cn.fujitsu.com \
--to=lig.fnst@cn.fujitsu.com \
--cc=dave@linux.vnet.ibm.com \
--cc=hpa@zytor.com \
--cc=jarkko.sakkinen@intel.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®