From: Stephen Warren <swarren@wwwdotorg.org>
To: Laxman Dewangan <ldewangan@nvidia.com>
Cc: "grant.likely@secretlab.ca" <grant.likely@secretlab.ca>,
"broonie@opensource.wolfsonmicro.com"
<broonie@opensource.wolfsonmicro.com>,
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:04:56 -0700 [thread overview]
Message-ID: <509D37B8.8020606@wwwdotorg.org> (raw)
In-Reply-To: <1352452052-13823-1-git-send-email-ldewangan@nvidia.com>
On 11/09/2012 02:07 AM, Laxman Dewangan wrote:
> Sequence compatible list for tegra20-slink driver to first
> look for Tegra30 and then Tegra20. Tegra30 have additional
> feature in HW which need to be utilize if it is provided from DT.
I don't object to this patch.
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).
next prev parent reply other threads:[~2012-11-09 17:04 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 [this message]
2012-11-09 17:10 ` Mark Brown
[not found] ` <20121109171008.GX23807-yzvPICuk2AATkU/dhu1WVueM+bqZidxxQQ4Iyu8u01E@public.gmane.org>
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
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=509D37B8.8020606@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;
as well as URLs for NNTP newsgroup(s).