From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Rami Rosen <ramirose@gmail.com>, dev@dpdk.org
Cc: stable@dpdk.org, xiao.w.wang@intel.com
Subject: Re: [dpdk-dev] [dpdk-stable] [PATCH] doc: fix an error in ifc NIC document
Date: Thu, 17 Jan 2019 15:57:36 +0000 [thread overview]
Message-ID: <623ce0b0-80ae-f3fb-524f-e50ef98de226@intel.com> (raw)
In-Reply-To: <1547736631-13231-1-git-send-email-ramirose@gmail.com>
On 1/17/2019 2:50 PM, Rami Rosen wrote:
> This patch fixes an error in ifc NIC document; a previous patch
> changed the semantics to use CONFIG_RTE_LIBRTE_IFC_PMD
> instread of CONFIG_RTE_LIBRTE_IFCVF_VDPA_PMD,
> but the ifc NIC doc file remained with the old name.
>
> Fixes: 4b614e9504a1 ("net/ifc: make driver name consistent")
> Cc: stable@dpdk.org
> Signed-off-by: Rami Rosen <ramirose@gmail.com>
Reviewed-by: Ferruh Yigit <ferruh.yigit@intel.com>
Applied to dpdk-next-net/master, thanks.
next prev parent reply other threads:[~2019-01-17 15:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-17 14:50 [dpdk-dev] " Rami Rosen
2019-01-17 15:57 ` Ferruh Yigit [this message]
2019-01-18 1:59 ` Wang, Xiao W
2019-01-18 8:39 ` Ferruh Yigit
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=623ce0b0-80ae-f3fb-524f-e50ef98de226@intel.com \
--to=ferruh.yigit@intel.com \
--cc=dev@dpdk.org \
--cc=ramirose@gmail.com \
--cc=stable@dpdk.org \
--cc=xiao.w.wang@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).