From: Sudeep Holla <sudeep.holla@arm.com>
To: Andrew Jones <ajones@ventanamicro.com>
Cc: Sunil V L <sunilvl@ventanamicro.com>,
linux-acpi@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-pm@vger.kernel.org, linux-riscv@lists.infradead.org,
Sudeep Holla <sudeep.holla@arm.com>,
"Rafael J . Wysocki" <rafael@kernel.org>,
Len Brown <lenb@kernel.org>, Anup Patel <anup@brainfault.org>,
Daniel Lezcano <daniel.lezcano@linaro.org>,
Paul Walmsley <paul.walmsley@sifive.com>,
Palmer Dabbelt <palmer@dabbelt.com>,
Albert Ou <aou@eecs.berkeley.edu>,
Conor Dooley <conor@kernel.org>,
Atish Kumar Patra <atishp@rivosinc.com>
Subject: Re: [PATCH -next 1/2] ACPI: Enable ACPI_PROCESSOR for RISC-V
Date: Thu, 11 Jan 2024 12:16:06 +0000 [thread overview]
Message-ID: <ZZ_cBlOSW9VCjkOv@bogus> (raw)
In-Reply-To: <20240111-bb411d2dd39eb859dd049fa0@orel>
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.
--
Regards,
Sudeep
WARNING: multiple messages have this Message-ID (diff)
From: Sudeep Holla <sudeep.holla@arm.com>
To: Andrew Jones <ajones@ventanamicro.com>
Cc: Daniel Lezcano <daniel.lezcano@linaro.org>,
linux-pm@vger.kernel.org, Anup Patel <anup@brainfault.org>,
"Rafael J . Wysocki" <rafael@kernel.org>,
Atish Kumar Patra <atishp@rivosinc.com>,
linux-kernel@vger.kernel.org, Conor Dooley <conor@kernel.org>,
linux-acpi@vger.kernel.org, Palmer Dabbelt <palmer@dabbelt.com>,
Paul Walmsley <paul.walmsley@sifive.com>,
Sudeep Holla <sudeep.holla@arm.com>,
linux-riscv@lists.infradead.org,
Albert Ou <aou@eecs.berkeley.edu>, Len Brown <lenb@kernel.org>
Subject: Re: [PATCH -next 1/2] ACPI: Enable ACPI_PROCESSOR for RISC-V
Date: Thu, 11 Jan 2024 12:16:06 +0000 [thread overview]
Message-ID: <ZZ_cBlOSW9VCjkOv@bogus> (raw)
In-Reply-To: <20240111-bb411d2dd39eb859dd049fa0@orel>
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.
--
Regards,
Sudeep
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
next prev parent reply other threads:[~2024-01-11 12:16 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-11 9:30 [PATCH -next 0/2] RISC-V: ACPI: Add LPI support Sunil V L
2024-01-11 9:30 ` Sunil V L
2024-01-11 9:30 ` [PATCH -next 1/2] ACPI: Enable ACPI_PROCESSOR for RISC-V Sunil V L
2024-01-11 9:30 ` Sunil V L
2024-01-11 10:00 ` Andrew Jones
2024-01-11 10:00 ` Andrew Jones
2024-01-11 11:29 ` Sunil V L
2024-01-11 11:29 ` Sunil V L
2024-01-11 12:16 ` Sudeep Holla [this message]
2024-01-11 12:16 ` Sudeep Holla
2024-01-11 12:28 ` Andrew Jones
2024-01-11 12:28 ` Andrew Jones
2024-01-11 9:30 ` [PATCH -next 2/2] cpuidle: RISC-V: Add ACPI LPI support Sunil V L
2024-01-11 9:30 ` Sunil V L
2024-01-11 10:19 ` Andrew Jones
2024-01-11 10:19 ` Andrew Jones
2024-01-11 11:31 ` Sunil V L
2024-01-11 11:31 ` Sunil V L
2024-01-12 5:05 ` Anup Patel
2024-01-12 5:05 ` Anup Patel
2024-01-15 5:07 ` Sunil V L
2024-01-15 5:07 ` Sunil V L
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=ZZ_cBlOSW9VCjkOv@bogus \
--to=sudeep.holla@arm.com \
--cc=ajones@ventanamicro.com \
--cc=anup@brainfault.org \
--cc=aou@eecs.berkeley.edu \
--cc=atishp@rivosinc.com \
--cc=conor@kernel.org \
--cc=daniel.lezcano@linaro.org \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=rafael@kernel.org \
--cc=sunilvl@ventanamicro.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.