All of lore.kernel.org
 help / color / mirror / Atom feed
From: Corentin LABBE <clabbe.montjoie@gmail.com>
To: herbert@gondor.apana.org.au, davem@davemloft.net,
	maxime.ripard@free-electrons.com, wens@csie.org
Cc: linux-crypto@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, stable <stable@vger.kernel.org>
Subject: Re: [PATCH] crypto: sun4i-ss: use spin_lock_irq{save|restore}
Date: Tue, 22 Mar 2016 18:48:00 +0100	[thread overview]
Message-ID: <56F18550.7030201@gmail.com> (raw)
In-Reply-To: <1458662694-25527-1-git-send-email-clabbe.montjoie@gmail.com>

Le 22/03/2016 17:04, LABBE Corentin a écrit :
> The current sun4i-ss driver is subject to data corruption when
> ciphering/deciphering.
> It occurs randomly on end of handled data.
> No root cause have been found and the only way to remove it is to replace
> all spin_lock_bh by they irq counterparts.
> 
> Signed-off-by: LABBE Corentin <clabbe.montjoie@gmail.com>
> Cc: stable <stable@vger.kernel.org>
> ---
>  drivers/crypto/sunxi-ss/sun4i-ss-cipher.c | 10 ++++++----
>  1 file changed, 6 insertions(+), 4 deletions(-)
> 

Hello

I have made a huge spelling problem, and didn't added Fixes tag.
I will resend it.
Sorry for the noise.

Regards

WARNING: multiple messages have this Message-ID (diff)
From: clabbe.montjoie@gmail.com (Corentin LABBE)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] crypto: sun4i-ss: use spin_lock_irq{save|restore}
Date: Tue, 22 Mar 2016 18:48:00 +0100	[thread overview]
Message-ID: <56F18550.7030201@gmail.com> (raw)
In-Reply-To: <1458662694-25527-1-git-send-email-clabbe.montjoie@gmail.com>

Le 22/03/2016 17:04, LABBE Corentin a ?crit :
> The current sun4i-ss driver is subject to data corruption when
> ciphering/deciphering.
> It occurs randomly on end of handled data.
> No root cause have been found and the only way to remove it is to replace
> all spin_lock_bh by they irq counterparts.
> 
> Signed-off-by: LABBE Corentin <clabbe.montjoie@gmail.com>
> Cc: stable <stable@vger.kernel.org>
> ---
>  drivers/crypto/sunxi-ss/sun4i-ss-cipher.c | 10 ++++++----
>  1 file changed, 6 insertions(+), 4 deletions(-)
> 

Hello

I have made a huge spelling problem, and didn't added Fixes tag.
I will resend it.
Sorry for the noise.

Regards

WARNING: multiple messages have this Message-ID (diff)
From: Corentin LABBE <clabbe.montjoie@gmail.com>
To: herbert@gondor.apana.org.au, davem@davemloft.net,
	maxime.ripard@free-electrons.com, wens@csie.org
Cc: linux-crypto@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, stable <stable@vger.kernel.org>
Subject: Re: [PATCH] crypto: sun4i-ss: use spin_lock_irq{save|restore}
Date: Tue, 22 Mar 2016 18:48:00 +0100	[thread overview]
Message-ID: <56F18550.7030201@gmail.com> (raw)
In-Reply-To: <1458662694-25527-1-git-send-email-clabbe.montjoie@gmail.com>

Le 22/03/2016 17:04, LABBE Corentin a �crit :
> The current sun4i-ss driver is subject to data corruption when
> ciphering/deciphering.
> It occurs randomly on end of handled data.
> No root cause have been found and the only way to remove it is to replace
> all spin_lock_bh by they irq counterparts.
> 
> Signed-off-by: LABBE Corentin <clabbe.montjoie@gmail.com>
> Cc: stable <stable@vger.kernel.org>
> ---
>  drivers/crypto/sunxi-ss/sun4i-ss-cipher.c | 10 ++++++----
>  1 file changed, 6 insertions(+), 4 deletions(-)
> 

Hello

I have made a huge spelling problem, and didn't added Fixes tag.
I will resend it.
Sorry for the noise.

Regards


  reply	other threads:[~2016-03-22 17:48 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-22 16:04 [PATCH] crypto: sun4i-ss: use spin_lock_irq{save|restore} LABBE Corentin
2016-03-22 16:04 ` LABBE Corentin
2016-03-22 17:48 ` Corentin LABBE [this message]
2016-03-22 17:48   ` Corentin LABBE
2016-03-22 17:48   ` Corentin LABBE

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=56F18550.7030201@gmail.com \
    --to=clabbe.montjoie@gmail.com \
    --cc=davem@davemloft.net \
    --cc=herbert@gondor.apana.org.au \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-crypto@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=maxime.ripard@free-electrons.com \
    --cc=stable@vger.kernel.org \
    --cc=wens@csie.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.