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  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Mon, 29 Dec 2014 16:03:16 +0000
From:	Mark Brown <broonie@...nel.org>
To:	Mika Westerberg <mika.westerberg@...ux.intel.com>
Cc:	linux-spi@...r.kernel.org, Grant Likely <grant.likely@...aro.org>,
	Rob Herring <robh+dt@...nel.org>,
	"Rafael J. Wysocki" <rjw@...ysocki.net>,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] spi/spidev: Convert to use unified device property API

On Mon, Dec 29, 2014 at 11:41:14AM +0200, Mika Westerberg wrote:
> This will allow the driver to match using DT compatible property if the
> device has ACPI _HID of "PRP0001" and accompanying "compatible" property
> listed in _DSD.

Which nobody should be doing since it's already totally broken for
something to be using this on the DT side except in the one case of the
Rohm device which is listed there.  I don't want to merge anything which
allows the breakage we're seeing with people putting spidev in their DTs
to be propagated into ACPI, at most we should have something that
specifically identifies individual devices only.

Download attachment "signature.asc" of type "application/pgp-signature" (474 bytes)

Powered by blists - more mailing lists