From: Sinan Kaya <okaya@kernel.org>
To: "Rafael J. Wysocki" <rafael@kernel.org>,
Bjorn Helgaas <bhelgaas@google.com>
Cc: ACPI Devel Maling List <linux-acpi@vger.kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
"H. Peter Anvin" <hpa@zytor.com>,
the arch/x86 maintainers <x86@kernel.org>,
"Rafael J. Wysocki" <rjw@rjwysocki.net>,
Len Brown <lenb@kernel.org>,
Robert Moore <robert.moore@intel.com>,
"Schmauss, Erik" <erik.schmauss@intel.com>,
Andy Shevchenko <andy.shevchenko@gmail.com>,
Jan Kiszka <jan.kiszka@siemens.com>,
otavio.pontes@intel.com, ckoenig.leichtzumerken@gmail.com,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux PCI <linux-pci@vger.kernel.org>,
devel@acpica.org
Subject: Re: [PATCH v8 3/4] PCI/ACPI: Allow ACPI to be built without CONFIG_PCI set
Date: Fri, 14 Dec 2018 11:29:42 -0500 [thread overview]
Message-ID: <578bb84f-ab1d-7e44-a6e1-7b0ff51c743a@kernel.org> (raw)
In-Reply-To: <CAJZ5v0j6u=E5xY-a=_D8wO5u=GOX9of3sG572pMSW+eB_e58Ow@mail.gmail.com>
On 12/14/2018 4:19 AM, Rafael J. Wysocki wrote:
> On Fri, Dec 14, 2018 at 4:13 AM Sinan Kaya<okaya@kernel.org> wrote:
>> We are compiling PCI code today for systems with ACPI and no PCI
>> device present. Remove the useless code and reduce the tight
>> dependency.
>>
>> Signed-off-by: Sinan Kaya<okaya@kernel.org>
> Bjorn, any objections here?
>
Found a breakage in arm64 build without CONFIG_PCI. I'll post a new version
soon.
prev parent reply other threads:[~2018-12-14 16:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20181214031252.28707-1-okaya@kernel.org>
2018-12-14 3:12 ` [PATCH v8 3/4] PCI/ACPI: Allow ACPI to be built without CONFIG_PCI set Sinan Kaya
2018-12-14 9:19 ` Rafael J. Wysocki
2018-12-14 16:29 ` 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=578bb84f-ab1d-7e44-a6e1-7b0ff51c743a@kernel.org \
--to=okaya@kernel.org \
--cc=andy.shevchenko@gmail.com \
--cc=bhelgaas@google.com \
--cc=bp@alien8.de \
--cc=ckoenig.leichtzumerken@gmail.com \
--cc=devel@acpica.org \
--cc=erik.schmauss@intel.com \
--cc=hpa@zytor.com \
--cc=jan.kiszka@siemens.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=otavio.pontes@intel.com \
--cc=rafael@kernel.org \
--cc=rjw@rjwysocki.net \
--cc=robert.moore@intel.com \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).