| 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
| ||
|
Message-ID: <20131204021703.GA8282@linux.intel.com> Date: Tue, 3 Dec 2013 18:17:03 -0800 From: "David E. Box" <david.e.box@...ux.intel.com> To: Matthew Garrett <mjg59@...f.ucam.org> Cc: rjw@...ysocki.net, linux-kernel@...r.kernel.org, platform-driver-x86@...r.kernel.org, linux-acpi@...r.kernel.org Subject: Re: [PATCHv2 2/2] ACPI/platform: Add ACPI ID for Intel MBI device On Wed, Dec 04, 2013 at 01:30:01AM +0000, Matthew Garrett wrote: > On Tue, Dec 03, 2013 at 03:59:38PM -0800, David E. Box wrote: > > From: "David E. Box" <david.e.box@...ux.intel.com> > > > > Adds ACPI ID for Intel IOSF-SB MailBox device found in BayTrail platforms. > > Little bit confused here. This is a new driver and only declares > modaliases for the ACPI IDs - why does it need to be added here? > This is per the requirement in Documentation/acpi/enumeration.txt: "Currently the kernel is not able to automatically determine from which ACPI device it should make the corresponding platform device so we need to add the ACPI device explicitly to acpi_platform_device_ids list defined in drivers/acpi/acpi_platform.c" Without adding the device here it would not be discovered and probe would not be called during init. David Box > -- > Matthew Garrett | mjg59@...f.ucam.org -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists