From: Jonathan Cameron <jonathan.cameron@huawei.com>
To: "Rafael J. Wysocki" <rjw@rjwysocki.net>
Cc: <linux-mm@kvack.org>, <linux-acpi@vger.kernel.org>,
<linux-kernel@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>, <x86@kernel.org>,
Keith Busch <keith.busch@intel.com>, <jglisse@redhat.com>,
<linuxarm@huawei.com>, Andrew Morton <akpm@linux-foundation.org>,
"Dan Williams" <dan.j.williams@intel.com>, <will@kernel.org>,
<lorenzo.pieralisi@arm.com>, <guohanjun@huawei.com>,
Ingo Molnar <mingo@kernel.org>
Subject: Re: [PATCH V5 1/4] ACPI: Support Generic Initiator only domains
Date: Tue, 12 Nov 2019 17:07:34 +0000 [thread overview]
Message-ID: <20191112170734.0000621a@huawei.com> (raw)
In-Reply-To: <1768519.laKBN70clK@kreacher>
On Thu, 7 Nov 2019 15:54:28 +0100
"Rafael J. Wysocki" <rjw@rjwysocki.net> wrote:
> On Friday, October 18, 2019 2:46:56 PM CET Jonathan Cameron wrote:
> > On Fri, 18 Oct 2019 12:18:33 +0200
> > "Rafael J. Wysocki" <rjw@rjwysocki.net> wrote:
> >
> > > On Friday, October 4, 2019 1:43:27 PM CEST Jonathan Cameron wrote:
> > > > Generic Initiators are a new ACPI concept that allows for the
> > > > description of proximity domains that contain a device which
> > > > performs memory access (such as a network card) but neither
> > > > host CPU nor Memory.
> > > >
> > > > This patch has the parsing code and provides the infrastructure
> > > > for an architecture to associate these new domains with their
> > > > nearest memory processing node.
> > > >
> > > > Signed-off-by: Jonathan Cameron <Jonathan.Cameron@huawei.com>
> > >
> > > This depends on the series from Dan at:
> > >
> > > https://lore.kernel.org/linux-acpi/CAPcyv4gBSX58CWH4HZ28w0_cZRzJrhgdEFHa2g8KDqyv8aFqZQ@mail.gmail.com/T/#m1acce3ae8f29f680c0d95fd1e840e703949fbc48
> > >
> > Hi Rafael,
> >
> > Yes. Cover letter mentions it was rebased on v4 of that series.
> >
> > > AFAICS, so please respin when that one hits the Linus' tree.
> >
> > Sure, though that pushes it out another cycle and it's beginning to
> > get a bit silly (just rebases since April).
> >
> > I guess it can't be helped given the series hits several trees.
>
> I've just applied the Dan's series and I can take patch [1/4] from this one,
> but for the [2-3/4] I'd like to get some ACKs from the arm64 and x86 people
> respectively.
Thanks Rafael!
Absolutely understood on the need for Acks.
For ARM let us try a few more CCs
+CC Will, Lorenzo, Hanjun.
Also Ingo on basis of showing a passing interest in the x86 patch
previously. Otherwise I think we have the x86 people most like to
comment already cc'd.
https://patchwork.kernel.org/cover/11174247/ has the full series.
I'd appreciate anyone who has time taking a look at these. The
actual actions in the architectures are very simple, but I may well
be missing some subtlety.
>
> Thanks!
>
Thanks,
Jonathan
next prev parent reply other threads:[~2019-11-12 17:07 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-04 11:43 [PATCH V5 0/4] ACPI: Support Generic Initiator proximity domains Jonathan Cameron
2019-10-04 11:43 ` [PATCH V5 1/4] ACPI: Support Generic Initiator only domains Jonathan Cameron
2019-10-18 10:18 ` Rafael J. Wysocki
2019-10-18 12:46 ` Jonathan Cameron
2019-11-07 14:54 ` Rafael J. Wysocki
2019-11-12 17:07 ` Jonathan Cameron [this message]
2019-11-12 17:55 ` Dan Williams
2019-11-13 9:47 ` Jonathan Cameron
2019-11-13 13:57 ` Tao Xu
2019-11-13 16:52 ` Dan Williams
2019-11-13 17:56 ` Jonathan Cameron
2019-11-13 17:48 ` Jonathan Cameron
2019-11-13 23:20 ` Dan Williams
2019-11-14 11:26 ` Jonathan Cameron
2019-11-16 20:45 ` Dan Williams
2019-11-18 17:18 ` Brice Goglin
2019-10-04 11:43 ` [PATCH V5 2/4] arm64: " Jonathan Cameron
2019-10-04 11:43 ` [PATCH V5 3/4] x86: Support Generic Initiator only proximity domains Jonathan Cameron
2019-10-07 14:55 ` Ingo Molnar
2019-10-08 11:17 ` Jonathan Cameron
2019-10-04 11:43 ` [PATCH V5 4/4] ACPI: Let ACPI know we support Generic Initiator Affinity Structures Jonathan Cameron
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=20191112170734.0000621a@huawei.com \
--to=jonathan.cameron@huawei.com \
--cc=akpm@linux-foundation.org \
--cc=dan.j.williams@intel.com \
--cc=guohanjun@huawei.com \
--cc=jglisse@redhat.com \
--cc=keith.busch@intel.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linuxarm@huawei.com \
--cc=lorenzo.pieralisi@arm.com \
--cc=mingo@kernel.org \
--cc=rjw@rjwysocki.net \
--cc=will@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;
as well as URLs for NNTP newsgroup(s).