From: Sinan Kaya <okaya@kernel.org>
To: Hanjun Guo <guohanjun@huawei.com>, linux-acpi@vger.kernel.org
Cc: Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>,
Hanjun Guo <hanjun.guo@linaro.org>,
Sudeep Holla <sudeep.holla@arm.com>,
"Rafael J. Wysocki" <rjw@rjwysocki.net>,
Len Brown <lenb@kernel.org>,
open list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v10 6/6] ACPI/IORT: Stub out ACS functions when CONFIG_PCI is not set
Date: Tue, 18 Dec 2018 03:46:17 +0100 [thread overview]
Message-ID: <80c186fe-e5ff-1d13-fad5-6386b21b45c4@kernel.org> (raw)
In-Reply-To: <40e31e86-a4ac-d9a6-d752-b04203d5ced7@huawei.com>
On 12/18/2018 3:14 AM, Hanjun Guo wrote:
> I prefer stub function for iort_enable_acs(), not adding #ifdef/#endif pair inside
> this function.
Yes, I'm reworking this per input from Lorenzo.
>
> By the way, there are other pci function called in iort.c, could you explain a
> little bit why no need to update other function calls in commit message?
I added few words about why other code was not stubbed out.
prev parent reply other threads:[~2018-12-18 2:46 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20181215010247.26101-1-okaya@kernel.org>
2018-12-15 1:02 ` [PATCH v10 1/6] ACPI: Allow CONFIG_PCI to be unset for reboot Sinan Kaya
2018-12-15 1:02 ` [PATCH v10 2/6] ACPI / OSL: Stub out acpi_os_(read/write)_pci_configurations() Sinan Kaya
2018-12-15 1:02 ` [PATCH v10 3/6] PCI/ACPI: Allow ACPI to be built without CONFIG_PCI set Sinan Kaya
2018-12-17 17:00 ` Ingo Molnar
2018-12-18 1:57 ` Sinan Kaya
2018-12-15 1:02 ` [PATCH v10 4/6] ACPICA: Remove PCI bits from ACPICA when CONFIG_PCI is unset Sinan Kaya
2018-12-15 1:02 ` [PATCH v10 5/6] arm64: select ACPI PCI code only both features are enabled Sinan Kaya
2018-12-17 10:04 ` Rafael J. Wysocki
2018-12-17 15:52 ` Catalin Marinas
2018-12-15 1:02 ` [PATCH v10 6/6] ACPI/IORT: Stub out ACS functions when CONFIG_PCI is not set Sinan Kaya
2018-12-17 10:04 ` Rafael J. Wysocki
2018-12-17 12:55 ` Lorenzo Pieralisi
2018-12-18 2:14 ` Hanjun Guo
2018-12-18 2:46 ` Sinan Kaya [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=80c186fe-e5ff-1d13-fad5-6386b21b45c4@kernel.org \
--to=okaya@kernel.org \
--cc=guohanjun@huawei.com \
--cc=hanjun.guo@linaro.org \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lorenzo.pieralisi@arm.com \
--cc=rjw@rjwysocki.net \
--cc=sudeep.holla@arm.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