From: Maxime Coquelin <maxime.coquelin@redhat.com>
To: Nicolas Chautru <nicolas.chautru@intel.com>, dev@dpdk.org
Cc: hernan.vargas@intel.com
Subject: Re: [PATCH v1 1/1] doc: update to Intel vRAN Boost PMD
Date: Mon, 6 Mar 2023 14:21:31 +0100 [thread overview]
Message-ID: <f4eac0bd-5f0a-87ce-8b92-0b6cde1556b6@redhat.com> (raw)
In-Reply-To: <8c3c14b4-c08a-00c4-4199-e090ef0b8c3e@redhat.com>
On 2/27/23 10:04, Maxime Coquelin wrote:
>
>
> On 2/24/23 19:20, Nicolas Chautru wrote:
>> Cosmetic change to refer explictly to the full name of the PMD
Fixed explictly -> explicitly
>> Intel vRAN Boost v1.
>> VRB1 acronym is only used as a prefix within the code.
>>
>> Signed-off-by: Nicolas Chautru <nicolas.chautru@intel.com>
>> ---
>> doc/guides/bbdevs/vrb1.rst | 6 +++---
>> 1 file changed, 3 insertions(+), 3 deletions(-)
>>
>> diff --git a/doc/guides/bbdevs/vrb1.rst b/doc/guides/bbdevs/vrb1.rst
>> index f5a9dff804..9c48d30964 100644
>> --- a/doc/guides/bbdevs/vrb1.rst
>> +++ b/doc/guides/bbdevs/vrb1.rst
>> @@ -104,7 +104,7 @@ Initialization
>> --------------
>> When the device first powers up, its PCI Physical Functions (PF)
>> -can be listed through these commands for VRB1:
>> +can be listed through these commands for Intel vRAN Boost v1:
>> .. code-block:: console
>> @@ -123,7 +123,7 @@ Install the DPDK igb_uio driver, bind it with the
>> PF PCI device ID and use
>> ``lspci`` to confirm the PF device is under use by ``igb_uio`` DPDK
>> UIO driver.
>> The igb_uio driver may be bound to the PF PCI device using one of
>> two methods
>> -for VRB1:
>> +for Intel vRAN Boost v1:
>> #. PCI functions (physical or virtual, depending on the use case)
>> can be bound
>> to the UIO driver by repeating this command for every function.
>> @@ -252,7 +252,7 @@ from the VF and not only limited to the PF as
>> captured above.
>> See for more details: https://github.com/intel/pf-bb-config
>> -Specifically for the bbdev VRB1 PMD, the command below can be used
>> +Specifically for the bbdev Intel vRAN Boost v1 PMD, the command below
>> can be used
>> (note that ACC200 was used previously to refer to VRB1):
>> .. code-block:: console
>
> Reviewed-by: Maxime Coquelin <maxime.coquelin@redhat.com>
>
> Thanks,
> Maxime
Applied to dpdk-next-baseband/for-main.
Thanks,
Maxime
prev parent reply other threads:[~2023-03-06 13:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-24 18:20 [PATCH v1 0/1] doc: PMD update Nicolas Chautru
2023-02-24 18:20 ` [PATCH v1 1/1] doc: update to Intel vRAN Boost PMD Nicolas Chautru
2023-02-27 9:04 ` Maxime Coquelin
2023-03-06 13:21 ` Maxime Coquelin [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=f4eac0bd-5f0a-87ce-8b92-0b6cde1556b6@redhat.com \
--to=maxime.coquelin@redhat.com \
--cc=dev@dpdk.org \
--cc=hernan.vargas@intel.com \
--cc=nicolas.chautru@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).