[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20240111-e3a13157f1869342e2c8e942@orel>
Date: Thu, 11 Jan 2024 13:28:09 +0100
From: Andrew Jones <ajones@...tanamicro.com>
To: Sudeep Holla <sudeep.holla@....com>
Cc: Sunil V L <sunilvl@...tanamicro.com>, linux-acpi@...r.kernel.org,
linux-kernel@...r.kernel.org, linux-pm@...r.kernel.org, linux-riscv@...ts.infradead.org,
"Rafael J . Wysocki" <rafael@...nel.org>, Len Brown <lenb@...nel.org>, Anup Patel <anup@...infault.org>,
Daniel Lezcano <daniel.lezcano@...aro.org>, Paul Walmsley <paul.walmsley@...ive.com>,
Palmer Dabbelt <palmer@...belt.com>, Albert Ou <aou@...s.berkeley.edu>,
Conor Dooley <conor@...nel.org>, Atish Kumar Patra <atishp@...osinc.com>
Subject: Re: Re: [PATCH -next 1/2] ACPI: Enable ACPI_PROCESSOR for RISC-V
On Thu, Jan 11, 2024 at 12:16:06PM +0000, Sudeep Holla wrote:
> On Thu, Jan 11, 2024 at 11:00:12AM +0100, Andrew Jones wrote:
>
> [...]
>
> > Also, interestingly, it looks like this ancient line
> >
> > obj-$(CONFIG_ACPI_PROCESSOR) += processor.o
> >
> > in drivers/acpi/Makefile should be removed,
>
> No
>
> > since there's no drivers/acpi/processor.c file.
>
> Correct, but ..
>
> > I guess the make process silently filters object files which don't have
> > corresponding source files?
>
> May be, but I doubt if that is the case here.
>
> processor.o is just aggregation of all processor_*.o and this will be
> the processor.ko when built as a module.
Oh, I see. I had tried looking for a processor.o after building, to see if
it was something like that, but it still didn't appear. It didn't occur to
me to also try ACPI_PROCESSOR as a module.
I'll go put my head in some sand now.
Thanks,
drew
Powered by blists - more mailing lists