From: Herbert Xu <herbert@gondor.apana.org.au>
To: Harsh Jain <harsh@chelsio.com>
Cc: hariprasad@chelsio.com, netdev@vger.kernel.org,
linux-crypto@vger.kernel.org
Subject: Re: [PATCH v1 0/4]crypto:chcr- Bug Fixes for 4.10
Date: Mon, 23 Jan 2017 21:39:46 +0800 [thread overview]
Message-ID: <20170123133946.GA19957@gondor.apana.org.au> (raw)
In-Reply-To: <cover.1484309965.git.harsh@chelsio.com>
On Fri, Jan 13, 2017 at 05:59:19PM +0530, Harsh Jain wrote:
> This patch series is based on Herbert's cryptodev-2.6 tree.
> It includes several critical bug fixes.
>
> Atul Gupta (3):
> crypto:chcr-Change flow IDs
> crypto:chcr- Fix panic on dma_unmap_sg
> crypto:chcr- Check device is allocated before use
> Julia Lawall (1):
> crypto:chcr-fix itnull.cocci warnings
Patches 2 and 3 look critical, but the other ones do not. Please
don't mix fixes targeted for this cycle with other patches.
Please resubmit them as two separate series.
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
prev parent reply other threads:[~2017-01-23 13:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-13 12:29 [PATCH v1 0/4]crypto:chcr- Bug Fixes for 4.10 Harsh Jain
2017-01-13 12:29 ` [PATCH v1 1/4] crypto:chcr-Change flow IDs Harsh Jain
2017-01-13 12:29 ` [PATCH v1 2/4] crypto:chcr- Fix panic on dma_unmap_sg Harsh Jain
2017-01-13 12:29 ` [PATCH v1 3/4] crypto:chcr- Check device is allocated before use Harsh Jain
2017-01-13 12:29 ` [PATCH v1 4/4] crypto:chcr-fix itnull.cocci warnings Harsh Jain
2017-01-23 13:39 ` Herbert Xu [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=20170123133946.GA19957@gondor.apana.org.au \
--to=herbert@gondor.apana.org.au \
--cc=hariprasad@chelsio.com \
--cc=harsh@chelsio.com \
--cc=linux-crypto@vger.kernel.org \
--cc=netdev@vger.kernel.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 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).