public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Stephen Warren <swarren@wwwdotorg.org>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
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, 09 Nov 2012 10:28:38 -0700	[thread overview]
Message-ID: <509D3D46.7060102@wwwdotorg.org> (raw)
In-Reply-To: <20121109171008.GX23807@opensource.wolfsonmicro.com>

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!

  reply	other threads:[~2012-11-09 17:31 UTC|newest]

Thread overview: 8+ 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 16:43 ` Mark Brown
2012-11-09 17:04 ` Stephen Warren
2012-11-09 17:10   ` Mark Brown
2012-11-09 17:28     ` Stephen Warren [this message]
2012-11-10 17:07       ` Thierry Reding
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=509D3D46.7060102@wwwdotorg.org \
    --to=swarren@wwwdotorg.org \
    --cc=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 \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox