From: Ferruh Yigit <ferruh.yigit@intel.com>
To: "Wang, Xiao W" <xiao.w.wang@intel.com>,
Rami Rosen <ramirose@gmail.com>, "dev@dpdk.org" <dev@dpdk.org>
Cc: "stable@dpdk.org" <stable@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH] doc: fix an error in ifc NIC document
Date: Fri, 18 Jan 2019 08:39:03 +0000 [thread overview]
Message-ID: <6dbc1024-2aaf-76d4-13a0-71d03e8c9eda@intel.com> (raw)
In-Reply-To: <B7F2E978279D1D49A3034B7786DACF407A4E22E6@SHSMSX101.ccr.corp.intel.com>
On 1/18/2019 1:59 AM, Wang, Xiao W wrote:
> Hi,
>
>> -----Original Message-----
>> From: Rami Rosen [mailto:ramirose@gmail.com]
>> Sent: Thursday, January 17, 2019 10:51 PM
>> To: dev@dpdk.org
>> Cc: stable@dpdk.org; Wang, Xiao W <xiao.w.wang@intel.com>; Rami Rosen
>> <ramirose@gmail.com>
>> Subject: [PATCH] doc: fix an error in ifc NIC document
>>
>> 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>
>> ---
>> doc/guides/nics/ifc.rst | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/doc/guides/nics/ifc.rst b/doc/guides/nics/ifc.rst
>> index bdf7b4e..317d9ff 100644
>> --- a/doc/guides/nics/ifc.rst
>> +++ b/doc/guides/nics/ifc.rst
>> @@ -19,7 +19,7 @@ Config File Options
>>
>> The following option can be modified in the ``config`` file.
>>
>> -- ``CONFIG_RTE_LIBRTE_IFCVF_VDPA_PMD`` (default ``y`` for linux)
>> +- ``CONFIG_RTE_LIBRTE_IFC_PMD`` (default ``y`` for linux)
>>
>> Toggle compilation of the ``librte_ifcvf_vdpa`` driver.
>
> Could we also squash below fix into this patch? Or we make a separate one since this patch is applied already.
>
> - Toggle compilation of the ``librte_ifcvf_vdpa`` driver.
> + Toggle compilation of the ``librte_pmd_ifc`` driver.
Thanks for update.
Squashed in next-net, please check.
prev parent reply other threads:[~2019-01-18 8:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-17 14:50 Rami Rosen
2019-01-17 15:57 ` [dpdk-dev] [dpdk-stable] " Ferruh Yigit
2019-01-18 1:59 ` [dpdk-dev] " Wang, Xiao W
2019-01-18 8:39 ` Ferruh Yigit [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=6dbc1024-2aaf-76d4-13a0-71d03e8c9eda@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).