From: Megha Dey <megha.dey@intel.com>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: tim.c.chen@linux.intel.com, davem@davemloft.net,
linux-crypto@vger.kernel.org, linux-kernel@vger.kernel.org,
fenghua.yu@intel.com
Subject: Re: [PATCH 1/7] crypto : stylistic cleanup in sha1-mb
Date: Tue, 31 May 2016 13:01:56 -0700 [thread overview]
Message-ID: <1464724916.9394.2.camel@megha-Z97X-UD7-TH> (raw)
In-Reply-To: <20160531081311.GA14591@gondor.apana.org.au>
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@linux.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@linux.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,
prev parent reply other threads:[~2016-05-31 19:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-20 0:43 [PATCH 1/7] crypto : stylistic cleanup in sha1-mb Megha Dey
2016-05-31 8:13 ` Herbert Xu
2016-05-31 20:01 ` Megha Dey [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=1464724916.9394.2.camel@megha-Z97X-UD7-TH \
--to=megha.dey@intel.com \
--cc=davem@davemloft.net \
--cc=fenghua.yu@intel.com \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tim.c.chen@linux.intel.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