From: "Rafael J. Wysocki" <rjw@rjwysocki.net>
To: Dan Williams <dan.j.williams@intel.com>
Cc: "Rafael J. Wysocki" <rafael@kernel.org>,
Ingo Molnar <mingo@redhat.com>, Len Brown <lenb@kernel.org>,
Keith Busch <kbusch@kernel.org>,
"Rafael J. Wysocki" <rafael.j.wysocki@intel.com>,
Dave Hansen <dave.hansen@linux.intel.com>,
Peter Zijlstra <peterz@infradead.org>,
Vishal Verma <vishal.l.verma@intel.com>,
Ard Biesheuvel <ard.biesheuvel@linaro.org>,
the arch/x86 maintainers <x86@kernel.org>,
linux-efi <linux-efi@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
ACPI Devel Maling List <linux-acpi@vger.kernel.org>,
Jonathan Cameron <Jonathan.Cameron@huawei.com>,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [PATCH v7 01/12] acpi/numa: Establish a new drivers/acpi/numa/ directory
Date: Mon, 28 Oct 2019 16:12:49 +0100 [thread overview]
Message-ID: <1666116.19LcctqB44@kreacher> (raw)
In-Reply-To: <CAPcyv4js1XqSe1kNeWob=ftscYFKQF+04PrKj7XDiEWUWvnMvQ@mail.gmail.com>
On Tuesday, October 22, 2019 6:48:12 PM CET Dan Williams wrote:
> On Tue, Oct 22, 2019 at 3:02 AM Rafael J. Wysocki <rafael@kernel.org> wrote:
> >
> > On Fri, Oct 18, 2019 at 11:25 AM Rafael J. Wysocki <rafael@kernel.org> wrote:
> > >
> > > On Wed, Oct 16, 2019 at 3:13 AM Dan Williams <dan.j.williams@intel.com> wrote:
> > > >
> > > > Currently hmat.c lives under an "hmat" directory which does not enhance
> > > > the description of the file. The initial motivation for giving hmat.c
> > > > its own directory was to delineate it as mm functionality in contrast to
> > > > ACPI device driver functionality.
> > > >
> > > > As ACPI continues to play an increasing role in conveying
> > > > memory location and performance topology information to the OS take the
> > > > opportunity to co-locate these NUMA relevant tables in a combined
> > > > directory.
> > > >
> > > > numa.c is renamed to srat.c and moved to drivers/acpi/numa/ along with
> > > > hmat.c.
> > > >
> > > > Cc: Len Brown <lenb@kernel.org>
> > > > Cc: Keith Busch <kbusch@kernel.org>
> > > > Acked-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
> > > > Reviewed-by: Dave Hansen <dave.hansen@linux.intel.com>
> > > > Signed-off-by: Dan Williams <dan.j.williams@intel.com>
> > >
> > > Please note that https://patchwork.kernel.org/patch/11078171/ is being
> > > pushed to Linus (it is overdue anyway), so if it is pulled, there will
> > > be a merge conflict with this patch.
> > >
> > > Respin maybe?
> >
> > Actually, would you mind it if I took this one into the ACPI tree right away?
> >
> > There's https://patchwork.kernel.org/patch/11198373/ queued up that,
> > again, will clash with it.
> >
> > Also, there is the generic Initiator proximity domains series from
> > Jonathan depending on it and I would like to move forward with that
> > one if there are no objections.
>
> Given Ard has acked all the EFI core and ARM changes can we proceed
> with merging the EFI Specific Purpose Memory series through Rafael's
> tree? It would need acks from x86 maintainers.
In the face of the lack of responses here, I think I will apply this patch
alone and expose a stable branch containing it in case somebody else wants
to pull it in.
Thanks!
next prev parent reply other threads:[~2019-10-28 15:12 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-16 0:59 [PATCH v7 00/12] EFI Specific Purpose Memory Support Dan Williams
2019-10-16 0:59 ` [PATCH v7 01/12] acpi/numa: Establish a new drivers/acpi/numa/ directory Dan Williams
2019-10-18 9:25 ` Rafael J. Wysocki
2019-10-22 10:01 ` Rafael J. Wysocki
2019-10-22 16:48 ` Dan Williams
2019-10-28 15:12 ` Rafael J. Wysocki [this message]
2019-10-29 3:06 ` Dan Williams
2019-10-16 0:59 ` [PATCH v7 02/12] efi: Enumerate EFI_MEMORY_SP Dan Williams
2019-10-16 0:59 ` [PATCH v7 03/12] x86/efi: Push EFI_MEMMAP check into leaf routines Dan Williams
2019-10-16 0:59 ` [PATCH v7 04/12] efi: Common enable/disable infrastructure for EFI soft reservation Dan Williams
2019-10-16 0:59 ` [PATCH v7 05/12] x86/efi: EFI soft reservation to E820 enumeration Dan Williams
2019-10-16 0:59 ` [PATCH v7 06/12] arm/efi: EFI soft reservation to memblock Dan Williams
2019-10-16 1:00 ` [PATCH v7 07/12] x86/efi: Add efi_fake_mem support for EFI_MEMORY_SP Dan Williams
2019-10-16 1:00 ` [PATCH v7 08/12] lib: Uplevel the pmem "region" ida to a global allocator Dan Williams
2019-10-16 1:00 ` [PATCH v7 09/12] dax: Fix alloc_dax_region() compile warning Dan Williams
2019-10-16 1:00 ` [PATCH v7 10/12] device-dax: Add a driver for "hmem" devices Dan Williams
2019-10-16 1:00 ` [PATCH v7 11/12] acpi/numa/hmat: Register HMAT at device_initcall level Dan Williams
2019-10-17 21:51 ` Rafael J. Wysocki
2019-10-16 1:00 ` [PATCH v7 12/12] acpi/numa/hmat: Register "soft reserved" memory as an "hmem" device Dan Williams
2019-10-17 21:54 ` Rafael J. Wysocki
2019-10-16 6:54 ` [PATCH v7 00/12] EFI Specific Purpose Memory Support Ard Biesheuvel
2019-10-16 15:33 ` Dan Williams
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=1666116.19LcctqB44@kreacher \
--to=rjw@rjwysocki.net \
--cc=Jonathan.Cameron@huawei.com \
--cc=ard.biesheuvel@linaro.org \
--cc=dan.j.williams@intel.com \
--cc=dave.hansen@linux.intel.com \
--cc=kbusch@kernel.org \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-efi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=rafael.j.wysocki@intel.com \
--cc=rafael@kernel.org \
--cc=tglx@linutronix.de \
--cc=vishal.l.verma@intel.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;
as well as URLs for NNTP newsgroup(s).