linux-kernel - Re: [PATCH] spi: tegra: sequence compatible strings as per preference

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <509D3D46.7060102@wwwdotorg.org>
Date:	Fri, 09 Nov 2012 10:28:38 -0700
From:	Stephen Warren <swarren@...dotorg.org>
To:	Mark Brown <broonie@...nsource.wolfsonmicro.com>
CC:	Laxman Dewangan <ldewangan@...dia.com>,
	"grant.likely@...retlab.ca" <grant.likely@...retlab.ca>,
	Stephen Warren <swarren@...dia.com>,
	"spi-devel-general@...ts.sourceforge.net" 
	<spi-devel-general@...ts.sourceforge.net>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] spi: tegra: sequence compatible strings as per preference

On 11/09/2012 10:10 AM, Mark Brown wrote:
> On Fri, Nov 09, 2012 at 10:04:56AM -0700, Stephen Warren wrote:
> 
>> However just FYI, it should not be necessary for correctness; The
>> DT matching order is supposed to be driven purely by the order of
>> the compatible values in the DT now, and not affected by the
>> order of values in the table. (This wasn't always the case, but
>> was a bug that was fixed IIRC by Thierry Reding).
> 
> I guess the driver is being used backported in older kernels which
> don't have that fix?

That sounds likely. Laxman, it'd be a good idea to track down the fix
to the DT matching code and backport it, so that hard-to debug issues
aren't caused by the lack of that patch!
--
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/