From: David Rientjes <rientjes@google.com>
To: li guang <lig.fnst@cn.fujitsu.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: Tue, 19 Feb 2013 23:00:08 -0800 (PST) [thread overview]
Message-ID: <alpine.DEB.2.02.1302192254440.27407@chino.kir.corp.google.com> (raw)
In-Reply-To: <1361330196.7859.51.camel@liguang.fnst.cn.fujitsu.com>
On Wed, 20 Feb 2013, li guang wrote:
> Yes, I know there's no new changes in my patch as I said before(not
> based on lasted), but as I try to apply my patch(1/4), it will do
> the right work to move current srat.c from arch/x86/mm/ to
> arch/x86/kernel/acpi/ regardless of what I based is not latest.
>
Sorry, but that makes no sense. Your patch cannot be used cleanly if
there have been subsequent changes to a hunk prior to applying it -- in
this case the hunk would be the entire file since you're removing it.
These patches would also be pushed by the x86 maintainers, who are not
cc'd on this patch, and I think it would be unfair to ask them to make up
for your inability to generate a bleeding edge patch with linux-next. The
changes already cited in this thread have been in linux-next for almost
two weeks, yet you refuse to rebase on top of them.
next prev parent reply other threads:[~2013-02-20 7:00 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
2013-02-20 3:04 ` David Rientjes
2013-02-20 3:16 ` li guang
2013-02-20 7:00 ` David Rientjes [this message]
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=alpine.DEB.2.02.1302192254440.27407@chino.kir.corp.google.com \
--to=rientjes@google.com \
--cc=isimatu.yasuaki@jp.fujitsu.com \
--cc=lig.fnst@cn.fujitsu.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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®