From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Stephen Warren <swarren@wwwdotorg.org>
Cc: Laxman Dewangan <ldewangan@nvidia.com>,
"grant.likely@secretlab.ca" <grant.likely@secretlab.ca>,
Stephen Warren <swarren@nvidia.com>,
"spi-devel-general@lists.sourceforge.net"
<spi-devel-general@lists.sourceforge.net>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] spi: tegra: sequence compatible strings as per preference
Date: Fri, 9 Nov 2012 17:10:08 +0000 [thread overview]
Message-ID: <20121109171008.GX23807@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <509D37B8.8020606@wwwdotorg.org>
[-- Attachment #1: Type: text/plain, Size: 471 bytes --]
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?
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2012-11-09 17:10 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-09 9:07 [PATCH] spi: tegra: sequence compatible strings as per preference Laxman Dewangan
2012-11-09 9:07 ` Laxman Dewangan
2012-11-09 16:43 ` Mark Brown
2012-11-09 17:04 ` Stephen Warren
2012-11-09 17:10 ` Mark Brown [this message]
[not found] ` <20121109171008.GX23807-yzvPICuk2AATkU/dhu1WVueM+bqZidxxQQ4Iyu8u01E@public.gmane.org>
2012-11-09 17:28 ` Stephen Warren
2012-11-09 17:28 ` Stephen Warren
2012-11-10 17:07 ` Thierry Reding
[not found] ` <20121110170741.GA17689-RM9K5IK7kjIQXX3q8xo1gnVAuStQJXxyR5q1nwbD4aMs9pC9oP6+/A@public.gmane.org>
2012-12-19 17:00 ` Grant Likely
2012-12-19 17:00 ` Grant Likely
2013-01-08 7:12 ` Thierry Reding
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20121109171008.GX23807@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=grant.likely@secretlab.ca \
--cc=ldewangan@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=spi-devel-general@lists.sourceforge.net \
--cc=swarren@nvidia.com \
--cc=swarren@wwwdotorg.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.