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
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Date:	Tue, 30 Dec 2014 11:23:25 +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 Tue, Dec 30, 2014 at 09:37:14AM +0200, Mika Westerberg wrote:
> On Mon, Dec 29, 2014 at 04:03:16PM +0000, Mark Brown wrote:

> > 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.

> It is pretty convenient for testing SPI bus and that's why I thought
> it would be good to have possibility to enumerate this in similar way
> than DT does but I understand your point.

My intention is to break this for DT, at least make it scream loud
warnings when it's used if not actually fail.

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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ