From: Sinan Kaya <okaya@kernel.org>
To: "Schmauss, Erik" <erik.schmauss@intel.com>,
"Rafael J. Wysocki" <rafael@kernel.org>
Cc: ACPI Devel Maling List <linux-acpi@vger.kernel.org>,
"Moore, Robert" <robert.moore@intel.com>,
"Wysocki, Rafael J" <rafael.j.wysocki@intel.com>,
Len Brown <lenb@kernel.org>,
"devel@acpica.org" <devel@acpica.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v6 5/5] ACPICA: Remove PCI bits from ACPICA when CONFIG_PCI is unset
Date: Wed, 12 Dec 2018 16:31:01 -0500 [thread overview]
Message-ID: <1cf7a2ce-0e1b-c329-a891-0cc9ae030f1b@kernel.org> (raw)
In-Reply-To: <CF6A88132359CE47947DB4C6E1709ED53C556C0D@ORSMSX122.amr.corp.intel.com>
On 12/12/2018 4:16 PM, Schmauss, Erik wrote:
>
>
>> -----Original Message-----
>> From: Rafael J. Wysocki [mailto:rafael@kernel.org]
>> Sent: Wednesday, December 12, 2018 1:07 PM
>> To: okaya@kernel.org; Schmauss, Erik <erik.schmauss@intel.com>
>> Cc: ACPI Devel Maling List <linux-acpi@vger.kernel.org>; Moore, Robert
>> <robert.moore@intel.com>; Wysocki, Rafael J <rafael.j.wysocki@intel.com>;
>> Len Brown <lenb@kernel.org>; devel@acpica.org; Linux Kernel Mailing List
>> <linux-kernel@vger.kernel.org>
>> Subject: Re: [PATCH v6 5/5] ACPICA: Remove PCI bits from ACPICA when
>> CONFIG_PCI is unset
>>
>> On Wed, Dec 12, 2018 at 8:34 PM Sinan Kaya <okaya@kernel.org> wrote:
>>>
>>> On 12/12/2018 2:02 PM, Schmauss, Erik wrote:
>>>>> ++ b/drivers/acpi/acpica/achware.h
>>>>> @@ -109,8 +109,17 @@ acpi_hw_enable_runtime_gpe_block(struct
>>>>> acpi_gpe_xrupt_info *gpe_xrupt_info,
>>>> CONFIG_PCI is a Linux-ism. We should stay with the OS-independent
>>>> nature of ACPICA. Please use ACPI_PCI_CONFIGURED and put it above
>> the comment like so:
>>>>
>>>> #ifdef ACPI_PCI_CONFIGURED
>>>
>>> Thanks for the feedback. My search for ACPI_PCI_CONFIGURED returned
>> nothing.
>>>
>>> git grep ACPI_PCI_CONFIGURED
>>>
>>> @Rafael,
>>>
>>> How do you want to handle this?
>>
>> I think what Eric suggested is effectively to introduce a new ACPICA symbol.
>> Erik?
>
> Yes, that's correct and you can add something like
>
> #ifdef CONFIG_PCI
> #define ACPI_PCI_CONFIGURED
> #endif
>
> in include/linux/platform/aclinux.h to enable it.
>
OK. Let me rework this and test.
prev parent reply other threads:[~2018-12-12 21:31 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20181212171941.7437-1-okaya@kernel.org>
2018-12-12 17:19 ` [PATCH v6 1/5] ACPI: Allow CONFIG_PCI to be unset for reboot Sinan Kaya
2018-12-12 17:19 ` [PATCH v6 2/5] ACPI / OSL: Stub out acpi_os_read_pci_configuration when CONFIG_PCI is unset Sinan Kaya
2018-12-12 17:19 ` [PATCH v6 3/5] ACPI / OSL: Stub out acpi_os_write_pci_configuration " Sinan Kaya
2018-12-12 17:19 ` [PATCH v6 4/5] PCI/ACPI: Allow ACPI to be built without CONFIG_PCI set Sinan Kaya
2018-12-12 17:19 ` [PATCH v6 5/5] ACPICA: Remove PCI bits from ACPICA when CONFIG_PCI is unset Sinan Kaya
2018-12-12 19:02 ` Schmauss, Erik
2018-12-12 19:34 ` Sinan Kaya
2018-12-12 21:06 ` Rafael J. Wysocki
2018-12-12 21:16 ` Schmauss, Erik
2018-12-12 21:31 ` 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=1cf7a2ce-0e1b-c329-a891-0cc9ae030f1b@kernel.org \
--to=okaya@kernel.org \
--cc=devel@acpica.org \
--cc=erik.schmauss@intel.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.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