lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Wed, 22 Mar 2017 18:42:39 +0100 From: "Rafael J. Wysocki" <rjw@...ysocki.net> To: Joerg Roedel <joro@...tes.org> Cc: Len Brown <lenb@...nel.org>, linux-acpi@...r.kernel.org, linux-kernel@...r.kernel.org, Joerg Roedel <jroedel@...e.de> Subject: Re: [PATCH 3/3] ACPI: Don't create a platform_device for IOAPIC/IOxAPIC On Wednesday, March 22, 2017 06:33:25 PM Joerg Roedel wrote: > From: Joerg Roedel <jroedel@...e.de> > > No platform-device is required for IO(x)APICs, so don't even > create them. > > Signed-off-by: Joerg Roedel <jroedel@...e.de> If we do this, I'd prefer not to do [2/3], because we'll introduce code that will be essentially dead 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? > + {"PNP0000", 0}, /* PIC */ > + {"PNP0100", 0}, /* Timer */ > + {"PNP0200", 0}, /* AT DMA Controller */ > + {"ACPI0009", 0}, /* IOxAPIC */ > + {"ACPI000A", 0}, /* IOAPIC */ > {"", 0}, > }; > > Thanks, Rafael
Powered by blists - more mailing lists