From: Joerg Roedel <jroedel@suse.de>
To: "Rafael J. Wysocki" <rjw@rjwysocki.net>
Cc: Joerg Roedel <joro@8bytes.org>, Len Brown <lenb@kernel.org>,
linux-acpi@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 3/3] ACPI: Don't create a platform_device for IOAPIC/IOxAPIC
Date: Wed, 22 Mar 2017 23:58:53 +0100 [thread overview]
Message-ID: <20170322225853.GH8329@suse.de> (raw)
In-Reply-To: <2232546.0OJbVJtxLm@aspire.rjw.lan>
Hi Rafael,
On Wed, Mar 22, 2017 at 06:42:39PM +0100, Rafael J. Wysocki wrote:
> On Wednesday, March 22, 2017 06:33:25 PM Joerg Roedel wrote:
> > From: Joerg Roedel <jroedel@suse.de>
> >
> > No platform-device is required for IO(x)APICs, so don't even
> > create them.
> >
> > Signed-off-by: Joerg Roedel <jroedel@suse.de>
>
> If we do this, I'd prefer not to do [2/3], because we'll introduce code that
> will be essentially dead then.
In this case the code in acpi_bus_attach() adding platform_devices is also
dead. Could it be removed then?
>
> > ---
> > drivers/acpi/acpi_platform.c | 8 +++++---
> > 1 file changed, 5 insertions(+), 3 deletions(-)
> >
> > diff --git a/drivers/acpi/acpi_platform.c b/drivers/acpi/acpi_platform.c
> > index b4c1a6a..03250e1 100644
> > --- a/drivers/acpi/acpi_platform.c
> > +++ b/drivers/acpi/acpi_platform.c
> > @@ -25,9 +25,11 @@
> > ACPI_MODULE_NAME("platform");
> >
> > static const struct acpi_device_id forbidden_id_list[] = {
> > - {"PNP0000", 0}, /* PIC */
> > - {"PNP0100", 0}, /* Timer */
> > - {"PNP0200", 0}, /* AT DMA Controller */
>
> Why do you change the existing entries?
Just to align the '0's in one column :)
Joerg
next prev parent reply other threads:[~2017-03-22 22:58 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-22 17:33 [PATCH 0/3] ACPI Fixes for Hotplug Joerg Roedel
2017-03-22 17:33 ` [PATCH 1/3] ACPI, ioapic: Clear on-stack resource before using it Joerg Roedel
2017-03-22 17:33 ` [PATCH 2/3] ACPI: Remove platform devices from a bus on removal Joerg Roedel
2017-04-19 6:50 ` joeyli
2017-04-19 6:54 ` joeyli
2017-03-22 17:33 ` [PATCH 3/3] ACPI: Don't create a platform_device for IOAPIC/IOxAPIC Joerg Roedel
2017-03-22 17:42 ` Rafael J. Wysocki
2017-03-22 22:58 ` Joerg Roedel [this message]
2017-03-22 23:41 ` Rafael J. Wysocki
2017-03-22 23:44 ` Rafael J. Wysocki
2017-03-22 23:58 ` Joerg Roedel
2017-03-23 1:06 ` Rafael J. Wysocki
2017-03-23 10:50 ` Joerg Roedel
2017-03-23 11:19 ` Rafael J. Wysocki
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=20170322225853.GH8329@suse.de \
--to=jroedel@suse.de \
--cc=joro@8bytes.org \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rjw@rjwysocki.net \
/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.