From: li guang <lig.fnst@cn.fujitsu.com>
To: David Rientjes <rientjes@google.com>
Cc: linux-kernel@vger.kernel.org, linux-acpi@vger.kernel.org,
x86@kernel.org, isimatu.yasuaki@jp.fujitsu.com
Subject: Re: [PATCH v4 1/4] acpi: move x86/mm/srat.c to x86/kernel/acpi/srat.c
Date: Wed, 20 Feb 2013 10:26:41 +0800 [thread overview]
Message-ID: <1361327201.7859.44.camel@liguang.fnst.cn.fujitsu.com> (raw)
In-Reply-To: <1361326913.7859.41.camel@liguang.fnst.cn.fujitsu.com>
在 2013-02-20三的 10:21 +0800，li guang写道：
> 在 2013-02-19二的 18:08 -0800，David Rientjes写道：
> > On Wed, 20 Feb 2013, li guang wrote:
> >
> > > > > This doesn't apply to Linus' tree nor does it apply to linux-next. Which
> > > > > tree are you basing this on?
> > > >
> > > > I did based on linux-next,
> > > > but it seems without commit 479a99a8e510c8839e0d3d3de8391f8bc61b9760
> > > > which you may want to see.
> > > > let me see why it missed.
> > >
> > > I pulled latest for linux-next
> > > and can apply my patches smoothly.
> > >
> >
> > No, it doesn't. From next-20130219, you're missing at least two patches:
> >
> > 3795e4893203 ("acpi, memory-hotplug: extend movablemem_map ranges to the end of node")
> > 9a561f4dfd70 ("acpi, memory-hotplug: support getting hotplug info from SRAT")
> >
> > I'm trying to be patient in reviewing your patches, but please double
> > check your work.
>
> I have to say my latest pull has these commit, and can apply
> successfully.
> really don't know why you can't apply.
>
I mean although my patches did not based on latest linux-next(miss
several commits), but as I can see, they can be applied to latest
linux-next (tag next-20130218) successfully.
next prev parent reply other threads:[~2013-02-20 2:26 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-15 2:23 [PATCH v4 0/4] acpi: do some changes for numa info liguang
2013-02-15 2:23 ` [PATCH v4 1/4] acpi: move x86/mm/srat.c to x86/kernel/acpi/srat.c liguang
2013-02-19 21:21 ` David Rientjes
2013-02-20 1:39 ` li guang
2013-02-20 1:51 ` li guang
2013-02-20 2:08 ` David Rientjes
2013-02-20 2:21 ` li guang
2013-02-20 2:26 ` li guang [this message]
2013-02-20 3:04 ` David Rientjes
2013-02-20 3:16 ` li guang
2013-02-20 7:00 ` David Rientjes
2013-02-20 7:05 ` li guang
2013-02-15 2:23 ` [PATCH v4 2/4] numa: avoid export acpi_numa variable liguang
2013-02-19 21:25 ` David Rientjes
2013-02-15 2:23 ` [PATCH v4 3/4] acpi: add clock_domain field to acpi_srat_cpu_affinity liguang
2013-02-15 2:23 ` [PATCH v4 4/4] remove include asm/acpi.h in process_driver.c liguang
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=1361327201.7859.44.camel@liguang.fnst.cn.fujitsu.com \
--to=lig.fnst@cn.fujitsu.com \
--cc=isimatu.yasuaki@jp.fujitsu.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rientjes@google.com \
--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®