All of lore.kernel.org
 help / color / mirror / Atom feed
From: Herbert Xu <herbert@gondor.apana.org.au>
To: Christophe Leroy <christophe.leroy@c-s.fr>
Cc: Horia Geanta <horia.geanta@nxp.com>,
	"David S. Miller" <davem@davemloft.net>,
	"linux-crypto@vger.kernel.org" <linux-crypto@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linuxppc-dev@lists.ozlabs.org" <linuxppc-dev@lists.ozlabs.org>
Subject: Re: [PATCH v2 4/4] crypto: talitos - drop icv_ool
Date: Thu, 13 Jun 2019 21:09:02 +0800	[thread overview]
Message-ID: <20190613130902.bswei465r4ey66gc@gondor.apana.org.au> (raw)
In-Reply-To: <b2db68d5-d89b-2f38-d5b4-7b7eccf68204@c-s.fr>

On Thu, Jun 13, 2019 at 02:28:51PM +0200, Christophe Leroy wrote:
> 
> 
> Le 13/06/2019 à 14:21, Horia Geanta a écrit :
> > On 6/11/2019 5:39 PM, Christophe Leroy wrote:
> > > icv_ool is not used anymore, drop it.
> > > 
> > > Fixes: 9cc87bc3613b ("crypto: talitos - fix AEAD processing")
> > I can't find this SHA1.
> > 
> > Are you referring to commit e345177ded17 ("crypto: talitos - fix AEAD processing.")?
> > 
> > Horia
> > 
> 
> Oops yes, that's the sha1 it had in my tree before it got merged.
> 
> Do I have to resend it or can Herbert just drop the wrong reference and take
> the following one:

Please resend since you're going to change the other patches too.

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

WARNING: multiple messages have this Message-ID (diff)
From: Herbert Xu <herbert@gondor.apana.org.au>
To: Christophe Leroy <christophe.leroy@c-s.fr>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linuxppc-dev@lists.ozlabs.org" <linuxppc-dev@lists.ozlabs.org>,
	"David S. Miller" <davem@davemloft.net>,
	Horia Geanta <horia.geanta@nxp.com>,
	"linux-crypto@vger.kernel.org" <linux-crypto@vger.kernel.org>
Subject: Re: [PATCH v2 4/4] crypto: talitos - drop icv_ool
Date: Thu, 13 Jun 2019 21:09:02 +0800	[thread overview]
Message-ID: <20190613130902.bswei465r4ey66gc@gondor.apana.org.au> (raw)
In-Reply-To: <b2db68d5-d89b-2f38-d5b4-7b7eccf68204@c-s.fr>

On Thu, Jun 13, 2019 at 02:28:51PM +0200, Christophe Leroy wrote:
> 
> 
> Le 13/06/2019 à 14:21, Horia Geanta a écrit :
> > On 6/11/2019 5:39 PM, Christophe Leroy wrote:
> > > icv_ool is not used anymore, drop it.
> > > 
> > > Fixes: 9cc87bc3613b ("crypto: talitos - fix AEAD processing")
> > I can't find this SHA1.
> > 
> > Are you referring to commit e345177ded17 ("crypto: talitos - fix AEAD processing.")?
> > 
> > Horia
> > 
> 
> Oops yes, that's the sha1 it had in my tree before it got merged.
> 
> Do I have to resend it or can Herbert just drop the wrong reference and take
> the following one:

Please resend since you're going to change the other patches too.

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:[~2019-06-13 15:18 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-11 14:39 [PATCH v2 0/4] Additional fixes on Talitos driver Christophe Leroy
2019-06-11 14:39 ` Christophe Leroy
2019-06-11 14:39 ` [PATCH v2 1/4] crypto: talitos - move struct talitos_edesc into talitos.h Christophe Leroy
2019-06-11 14:39   ` Christophe Leroy
2019-06-13 12:13   ` Horia Geanta
2019-06-13 12:13     ` Horia Geanta
2019-06-13 12:16     ` Christophe Leroy
2019-06-13 12:16       ` Christophe Leroy
2019-06-13 12:24       ` Horia Geanta
2019-06-13 12:24         ` Horia Geanta
2019-06-13 12:32         ` Christophe Leroy
2019-06-13 12:32           ` Christophe Leroy
2019-06-13 12:39           ` Horia Geanta
2019-06-13 12:39             ` Horia Geanta
2019-06-13 12:50             ` Christophe Leroy
2019-06-13 12:50               ` Christophe Leroy
2019-06-11 14:39 ` [PATCH v2 2/4] crypto: talitos - fix hash on SEC1 Christophe Leroy
2019-06-11 14:39   ` Christophe Leroy
2019-06-11 14:39 ` [PATCH v2 3/4] crypto: talitos - eliminate unneeded 'done' functions at build time Christophe Leroy
2019-06-11 14:39   ` Christophe Leroy
2019-06-13 12:16   ` Horia Geanta
2019-06-13 12:16     ` Horia Geanta
2019-06-11 14:39 ` [PATCH v2 4/4] crypto: talitos - drop icv_ool Christophe Leroy
2019-06-11 14:39   ` Christophe Leroy
2019-06-13 12:21   ` Horia Geanta
2019-06-13 12:21     ` Horia Geanta
2019-06-13 12:28     ` Christophe Leroy
2019-06-13 12:28       ` Christophe Leroy
2019-06-13 13:09       ` Herbert Xu [this message]
2019-06-13 13:09         ` Herbert Xu
2019-06-11 15:37 ` [PATCH v2 0/4] Additional fixes on Talitos driver Horia Geanta
2019-06-11 15:37   ` Horia Geanta
2019-06-11 15:40   ` Christophe Leroy
2019-06-11 15:40     ` Christophe Leroy
2019-06-11 16:30     ` Horia Geanta
2019-06-11 16:30       ` Horia Geanta
2019-06-11 17:16       ` Christophe Leroy
2019-06-11 17:16         ` Christophe Leroy
2019-06-12  5:52       ` Christophe Leroy
2019-06-12  5:52         ` Christophe Leroy
2019-06-12 13:59         ` Horia Geanta
2019-06-12 13:59           ` Horia Geanta
2019-06-13  4:57           ` Christophe Leroy
2019-06-13  4:57             ` Christophe Leroy

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=20190613130902.bswei465r4ey66gc@gondor.apana.org.au \
    --to=herbert@gondor.apana.org.au \
    --cc=christophe.leroy@c-s.fr \
    --cc=davem@davemloft.net \
    --cc=horia.geanta@nxp.com \
    --cc=linux-crypto@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxppc-dev@lists.ozlabs.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.