From: Tadeusz Struk <tadeusz.struk@intel.com>
To: herbert@gondor.apana.org.au
Cc: pingchao.yang@intel.com, linux-crypto@vger.kernel.org
Subject: Re: [PATCH] crypto: qat - update init_esram for C3xxx dev type
Date: Fri, 8 Jan 2016 10:35:46 -0800 [thread overview]
Message-ID: <56900182.2080808@intel.com> (raw)
In-Reply-To: <1452277194-4804-1-git-send-email-tadeusz.struk@intel.com>
On 01/08/2016 10:19 AM, Tadeusz Struk wrote:
> There is no esram on C3xxx devices so we don't need to wait for
> it to initialize.
>
> Signed-off-by: Tadeusz Struk <tadeusz.struk@intel.com>
> ---
> drivers/crypto/qat/qat_common/qat_hal.c | 3 +++
> 1 file changed, 3 insertions(+)
Hi Herbert,
This one is generated on top of Pingchao's patch "crypto: qat - fix timeout issues"
https://patchwork.kernel.org/patch/7972981/
Thanks
--
TS
next prev parent reply other threads:[~2016-01-08 18:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-08 18:19 [PATCH] crypto: qat - update init_esram for C3xxx dev type Tadeusz Struk
2016-01-08 18:35 ` Tadeusz Struk [this message]
2016-01-15 18:29 ` Tadeusz Struk
2016-01-18 15:23 ` Herbert Xu
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=56900182.2080808@intel.com \
--to=tadeusz.struk@intel.com \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--cc=pingchao.yang@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;
as well as URLs for NNTP newsgroup(s).