LinuxPPC-Dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Herbert Xu <herbert@gondor.apana.org.au>
To: Grant Likely <grant.likely@secretlab.ca>
Cc: Steve Cornelius <sec@pobox.com>,
	devicetree-discuss@lists.ozlabs.org,
	linux-crypto@vger.kernel.org,
	Scott Wood <scottwood@freescale.com>,
	linuxppc-dev@lists.ozlabs.org,
	Kumar Gala <kumar.gala@freescale.com>
Subject: Re: [PATCH] crypto: caam - de-CHIP-ify device tree compatibles
Date: Wed, 23 Mar 2011 21:24:09 +0800	[thread overview]
Message-ID: <20110323132409.GD4374@gondor.apana.org.au> (raw)
In-Reply-To: <20110316005951.GA18791@angua.secretlab.ca>

On Tue, Mar 15, 2011 at 06:59:51PM -0600, Grant Likely wrote:
> On Tue, Mar 15, 2011 at 04:52:20PM -0500, Kim Phillips wrote:
> > - all the integration parameters have been captured by the binding.
> > - the block name really uniquely identifies this hardware.
> > 
> > Some advocate putting SoC names everywhere in case software needs
> > to work around some chip-specific bug, but more precise SoC
> > information already exists in SVR, and board information already
> > exists in the top-level device tree node.
> > 
> > Note that sometimes the SoC name is a worse identifier than the
> > block version, as the block version can change between revisions
> > of the same SoC.
> > 
> > As a matter of historical reference, neither SEC versions 2.x
> > nor 3.x (driven by talitos) ever needed CHIP references.
> > 
> > Signed-off-by: Kim Phillips <kim.phillips@freescale.com>
> 
> <sigh>  Very well.  As long as some level of versioning is used on the
> compatible values, I guess I can live with it.
> 
> Acked-off-by: Grant Likely <grant.likely@secretlab.ca>

Patch applied.  Thanks!
-- 
Email: Herbert Xu <herbert@gondor.apana.org.au>
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt

      reply	other threads:[~2011-03-23 13:24 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-15 21:52 [PATCH] crypto: caam - de-CHIP-ify device tree compatibles Kim Phillips
2011-03-16  0:59 ` Grant Likely
2011-03-23 13:24   ` Herbert Xu [this message]

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=20110323132409.GD4374@gondor.apana.org.au \
    --to=herbert@gondor.apana.org.au \
    --cc=devicetree-discuss@lists.ozlabs.org \
    --cc=grant.likely@secretlab.ca \
    --cc=kumar.gala@freescale.com \
    --cc=linux-crypto@vger.kernel.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=scottwood@freescale.com \
    --cc=sec@pobox.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