From: Ferruh Yigit <ferruh.yigit@intel.com>
To: stable-bounces@dpdk.org, dev@dpdk.org
Cc: akhil.goyal@nxp.com, arkadiuszx.kusztal@intel.com, stable@dpdk.org
Subject: Re: [dpdk-dev] [dpdk-stable] [PATCH] lib/cryptodev: fix library version
Date: Mon, 15 Oct 2018 14:18:33 +0100 [thread overview]
Message-ID: <cbbb51fc-13b4-2016-579f-3701e7fcc19b@intel.com> (raw)
In-Reply-To: <20181015112816.57011-1-roy.fan.zhang@intel.com>
On 10/15/2018 12:28 PM, stable-bounces@dpdk.org wrote:
> This patch fixes the cryptodev library version number that was
> missed updating in DPDK 18.08.
>
> Fixes: a4493be5bdfa ("cryptodev: replace bus specific struct with generic dev")
> Cc: stable@dpdk.org
>
> Signed-off-by: Fan Zhang <roy.fan.zhang@intel.com>
Reviewed-by: Ferruh Yigit <ferruh.yigit@intel.com>
lib/ can be dropped from title:
cryptodev: fix library version
next prev parent reply other threads:[~2018-10-15 13:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-15 11:28 [dpdk-dev] " Fan Zhang
2018-10-15 13:18 ` Ferruh Yigit [this message]
2018-10-16 14:36 ` [dpdk-dev] [dpdk-stable] " 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=cbbb51fc-13b4-2016-579f-3701e7fcc19b@intel.com \
--to=ferruh.yigit@intel.com \
--cc=akhil.goyal@nxp.com \
--cc=arkadiuszx.kusztal@intel.com \
--cc=dev@dpdk.org \
--cc=stable-bounces@dpdk.org \
--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).