[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <1464724916.9394.2.camel@megha-Z97X-UD7-TH>
Date: Tue, 31 May 2016 13:01:56 -0700
From: Megha Dey <megha.dey@...el.com>
To: Herbert Xu <herbert@...dor.apana.org.au>
Cc: tim.c.chen@...ux.intel.com, davem@...emloft.net,
linux-crypto@...r.kernel.org, linux-kernel@...r.kernel.org,
fenghua.yu@...el.com
Subject: Re: [PATCH 1/7] crypto : stylistic cleanup in sha1-mb
On Tue, 2016-05-31 at 16:13 +0800, Herbert Xu wrote:
> On Thu, May 19, 2016 at 05:43:04PM -0700, Megha Dey wrote:
> > From: Megha Dey <megha.dey@...ux.intel.com>
> >
> > Currently there are several checkpatch warnings in the sha1_mb.c file:
> > 'WARNING: line over 80 characters' in the sha1_mb.c file. Also, the
> > syntax of some multi-line comments are not correct. This patch fixes
> > these issues.
> >
> > Signed-off-by: Megha Dey <megha.dey@...ux.intel.com>
>
> This patch says 1/7 but there is no cover letter and I've only
> seen patches 1 and 2. What's going on?
Herbert , I had 7 patches for the async+avx2 sha256-mb implementation. I
had sent just the async related changes here. However, I will resend the
patches as 2 sets. One which has only async implementation changes and
the other which has only sha256-mb avx2 implementation changes. Please
disregard the current patches and review the ones I will be sending
again.
>
> Cheers,
Powered by blists - more mailing lists