From: "De Lara Guarch, Pablo" <pablo.de.lara.guarch@intel.com>
To: "Trahe, Fiona" <fiona.trahe@intel.com>,
"Eads, Gage" <gage.eads@intel.com>, "dev@dpdk.org" <dev@dpdk.org>
Cc: "Griffin, John" <john.griffin@intel.com>,
"Jain, Deepak K" <deepak.k.jain@intel.com>,
"stable@dpdk.org" <stable@dpdk.org>,
"Trahe, Fiona" <fiona.trahe@intel.com>
Subject: Re: [dpdk-stable] [PATCH] crypto/qat: fix dequeue count stats retrieval
Date: Fri, 28 Apr 2017 07:54:25 +0000 [thread overview]
Message-ID: <E115CCD9D858EF4F90C690B0DCB4D89747812F13@IRSMSX108.ger.corp.intel.com> (raw)
In-Reply-To: <348A99DA5F5B7549AA880327E580B435891EBBFC@IRSMSX101.ger.corp.intel.com>
> -----Original Message-----
> From: stable [mailto:stable-bounces@dpdk.org] On Behalf Of Trahe, Fiona
> Sent: Thursday, April 27, 2017 4:47 PM
> To: Eads, Gage; dev@dpdk.org
> Cc: Griffin, John; Jain, Deepak K; stable@dpdk.org; Trahe, Fiona
> Subject: Re: [dpdk-stable] [PATCH] crypto/qat: fix dequeue count stats
> retrieval
>
>
>
> > -----Original Message-----
> > From: Eads, Gage
> > Sent: Thursday, April 27, 2017 4:31 PM
> > To: dev@dpdk.org
> > Cc: Griffin, John <john.griffin@intel.com>; Trahe, Fiona
> > <fiona.trahe@intel.com>; Jain, Deepak K <deepak.k.jain@intel.com>;
> > stable@dpdk.org
> > Subject: [PATCH] crypto/qat: fix dequeue count stats retrieval
> >
> > The QAT device's dequeued_count and dequeue_err_count stats were
> > incorrectly assigned the enqueued_count and enqueue_err_count values,
> > respectively.
> >
> > Signed-off-by: Gage Eads <gage.eads@intel.com>
> > Fixes: 1703e94a ("qat: add driver for QuickAssist devices")
>
> Acked-by: Fiona Trahe <fiona.trahe@intel.com>
Fixed "fixes line" with 6 SHA-1 bytes: 1703e94ac5ce
Added Cc: stable@dpdk.org
Applied to dpdk-next-crypto.
Thanks,
Pablo
prev parent reply other threads:[~2017-04-28 7:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-27 15:31 Gage Eads
2017-04-27 15:47 ` Trahe, Fiona
2017-04-28 7:54 ` De Lara Guarch, Pablo [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=E115CCD9D858EF4F90C690B0DCB4D89747812F13@IRSMSX108.ger.corp.intel.com \
--to=pablo.de.lara.guarch@intel.com \
--cc=deepak.k.jain@intel.com \
--cc=dev@dpdk.org \
--cc=fiona.trahe@intel.com \
--cc=gage.eads@intel.com \
--cc=john.griffin@intel.com \
--cc=stable@dpdk.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).