linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Kim Phillips <kim.phillips@freescale.com>
To: Shengzhou Liu <Shengzhou.Liu@freescale.com>
Cc: linuxppc-dev@lists.ozlabs.org, Liu Shuo <shuo.liu@freescale.com>
Subject: Re: [PATCH] powerpc/dts: fix the compatible string of sec 4.0
Date: Tue, 6 Mar 2012 11:41:12 -0600	[thread overview]
Message-ID: <20120306114112.9af0bb75863f36b82e908e3d@freescale.com> (raw)
In-Reply-To: <1331018476-27798-1-git-send-email-Shengzhou.Liu@freescale.com>

On Tue, 6 Mar 2012 15:21:16 +0800
Shengzhou Liu <Shengzhou.Liu@freescale.com> wrote:

> From: Liu Shuo <shuo.liu@freescale.com>
> 
> Fix the compatible string of sec 4.0 to match with CAMM driver according
> to the documentation file Documentation/devicetree/bindings/crypto/fsl-sec4.txt.

s/the documentation file//, since it's pretty obvious from the
pathname.

Also, if you wrap your commit text to 75 chars, then people won't
have to use the left- and right-arrow keys when browsing git log.

> +++ b/arch/powerpc/boot/dts/fsl/pq3-sec4.4-0.dtsi
> @@ -33,32 +33,32 @@
>   */
>  
>  crypto@30000 {
> -	compatible = "fsl,sec4.4", "fsl,sec4.0";
> +	compatible = "fsl,sec-v4.4", "fsl,sec-v4.0";

so I've tracked the original error down to v3.2-rc3-18-g5652520,
which means v3.2 was released with the error.  Consequently, the
driver should also be updated to check for "fsl,sec-v4.0", and,
failing that, check for "fsl,sec4.0".  The fix should also be sent
to stable@kernel.org [1].

Thanks,

Kim

[1] see Documentation/stable_kernel_rules.txt

      parent reply	other threads:[~2012-03-06 17:43 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-06  7:21 [PATCH] powerpc/dts: fix the compatible string of sec 4.0 Shengzhou Liu
2012-03-06 11:45 ` Kumar Gala
2012-03-06 17:41 ` Kim Phillips [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=20120306114112.9af0bb75863f36b82e908e3d@freescale.com \
    --to=kim.phillips@freescale.com \
    --cc=Shengzhou.Liu@freescale.com \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=shuo.liu@freescale.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).