[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAJZ5v0j_-iSqiysZiW=J8Y5FCAjnPC7ZvevrLsYhngWr6mT6GQ@mail.gmail.com>
Date: Tue, 22 Oct 2019 12:01:42 +0200
From: "Rafael J. Wysocki" <rafael@...nel.org>
To: Dan Williams <dan.j.williams@...el.com>
Cc: Ingo Molnar <mingo@...hat.com>, Len Brown <lenb@...nel.org>,
Keith Busch <kbusch@...nel.org>,
"Rafael J. Wysocki" <rafael.j.wysocki@...el.com>,
Dave Hansen <dave.hansen@...ux.intel.com>,
Peter Zijlstra <peterz@...radead.org>,
Vishal Verma <vishal.l.verma@...el.com>,
Ard Biesheuvel <ard.biesheuvel@...aro.org>,
"the arch/x86 maintainers" <x86@...nel.org>,
linux-efi <linux-efi@...r.kernel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
ACPI Devel Maling List <linux-acpi@...r.kernel.org>,
Jonathan Cameron <Jonathan.Cameron@...wei.com>
Subject: Re: [PATCH v7 01/12] acpi/numa: Establish a new drivers/acpi/numa/ directory
On Fri, Oct 18, 2019 at 11:25 AM Rafael J. Wysocki <rafael@...nel.org> wrote:
>
> On Wed, Oct 16, 2019 at 3:13 AM Dan Williams <dan.j.williams@...el.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@...nel.org>
> > Cc: Keith Busch <kbusch@...nel.org>
> > Acked-by: Rafael J. Wysocki <rafael.j.wysocki@...el.com>
> > Reviewed-by: Dave Hansen <dave.hansen@...ux.intel.com>
> > Signed-off-by: Dan Williams <dan.j.williams@...el.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.
Powered by blists - more mailing lists