From: Dave Jiang <dave.jiang@intel.com>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: "Rafael J. Wysocki" <rafael@kernel.org>,
Sam Edwards <cfsworks@gmail.com>, Len Brown <lenb@kernel.org>,
Robert Moore <robert.moore@intel.com>,
"Jonathan Cameron" <Jonathan.Cameron@huawei.com>,
Dan Williams <dan.j.williams@intel.com>,
Hanjun Guo <guohanjun@huawei.com>, Arnd Bergmann <arnd@arndb.de>,
"Rafael J. Wysocki" <rafael.j.wysocki@intel.com>,
<linux-acpi@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH] ACPI: acenv: Permit compilation from within the kernel
Date: Tue, 21 Nov 2023 09:01:19 -0700 [thread overview]
Message-ID: <36a3693c-0dae-4ea2-8b7d-f1a0f5148202@intel.com> (raw)
In-Reply-To: <CACRpkdbz=a7yoJdBOrgJXth53d=F7+eQCu7KofUW8s1rBY=Veg@mail.gmail.com>
On 11/21/23 06:32, Linus Walleij wrote:
> On Mon, Nov 20, 2023 at 5:53 PM Dave Jiang <dave.jiang@intel.com> wrote:
>
>> However, if I move fw_table.h in linux/acpi.h below include of asm/acpi.h, then we
>> can build successfully w/o including acpi/acpi.h in fw_table.h.
>
> This looks reasonable to me, can you send a formal patch so I can test?
https://lore.kernel.org/linux-acpi/170058229266.2356592.11579977558324549374.stgit@djiang5-mobl3/
Thanks!
>
> Yours,
> Linus Walleij
prev parent reply other threads:[~2023-11-21 16:01 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-13 23:08 Linus Walleij
2023-11-14 18:09 ` Sam Edwards
2023-11-14 20:20 ` Linus Walleij
2023-11-20 15:25 ` Sam Protsenko
2023-11-20 15:46 ` Rafael J. Wysocki
2023-11-20 16:19 ` Dave Jiang
2023-11-20 16:38 ` Rafael J. Wysocki
2023-11-20 16:53 ` Dave Jiang
2023-11-21 13:32 ` Linus Walleij
2023-11-21 16:01 ` Dave Jiang [this message]
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=36a3693c-0dae-4ea2-8b7d-f1a0f5148202@intel.com \
--to=dave.jiang@intel.com \
--cc=Jonathan.Cameron@huawei.com \
--cc=arnd@arndb.de \
--cc=cfsworks@gmail.com \
--cc=dan.j.williams@intel.com \
--cc=guohanjun@huawei.com \
--cc=lenb@kernel.org \
--cc=linus.walleij@linaro.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rafael.j.wysocki@intel.com \
--cc=rafael@kernel.org \
--cc=robert.moore@intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®