mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: David Rientjes <rientjes@google.com>
To: liguang <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 13:21:22 -0800 (PST)	[thread overview]
Message-ID: <alpine.DEB.2.02.1302191320410.6322@chino.kir.corp.google.com> (raw)
In-Reply-To: <1360894992-14818-2-git-send-email-lig.fnst@cn.fujitsu.com>

On Fri, 15 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>

This doesn't apply to Linus' tree nor does it apply to linux-next.  Which 
tree are you basing this on?

  reply	other threads:[~2013-02-19 21:21 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 [this message]
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
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.1302191320410.6322@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®