From: "Trahe, Fiona" <fiona.trahe@intel.com>
To: "Daly, Lee" <lee.daly@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>, "stable@dpdk.org" <stable@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH] lib/compress: fix incorrect structure comment
Date: Tue, 27 Nov 2018 15:17:52 +0000 [thread overview]
Message-ID: <348A99DA5F5B7549AA880327E580B435896813A3@IRSMSX101.ger.corp.intel.com> (raw)
In-Reply-To: <1543331424-53895-1-git-send-email-lee.daly@intel.com>
> -----Original Message-----
> From: Daly, Lee
> Sent: Tuesday, November 27, 2018 8:10 AM
> To: Trahe, Fiona <fiona.trahe@intel.com>
> Cc: dev@dpdk.org; Daly, Lee <lee.daly@intel.com>; stable@dpdk.org
> Subject: [PATCH] lib/compress: fix incorrect structure comment
>
> Fixes incorrect comment on compressdev rte_comp_op structure element.
> Comment needed to be updated to be compliant with the use of
> chained mbufs.
>
> Fixes: f87bdc1ddcf4 ("compressdev: add compression specific data")
> Cc: stable@dpdk.org
> Cc: fiona.trahe@intel.com
>
> Signed-off-by: Lee Daly <lee.daly@intel.com>
Acked-by: Fiona Trahe <fiona.trahe@intel.com>
next prev parent reply other threads:[~2018-11-27 15:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-27 15:10 Lee Daly
2018-11-27 15:17 ` Trahe, Fiona [this message]
2018-12-18 10:22 ` Akhil Goyal
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=348A99DA5F5B7549AA880327E580B435896813A3@IRSMSX101.ger.corp.intel.com \
--to=fiona.trahe@intel.com \
--cc=dev@dpdk.org \
--cc=lee.daly@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).