From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Jerin Jacob <jerinjacobk@gmail.com>,
Tomasz Duszynski <tduszynski@marvell.com>
Cc: dpdk-dev <dev@dpdk.org>,
Nithin Dabilpuram <ndabilpuram@marvell.com>,
Kiran Kumar K <kirankumark@marvell.com>,
Sunil Kumar Kori <skori@marvell.com>,
Satha Rao <skoteshwar@marvell.com>,
Thomas Monjalon <thomas@monjalon.net>,
Jerin Jacob <jerinj@marvell.com>
Subject: Re: [PATCH] common/cnxk: support B0 variant
Date: Fri, 25 Feb 2022 10:03:22 +0000 [thread overview]
Message-ID: <e7e47277-e2fe-95e4-4e04-660b20db9b22@intel.com> (raw)
In-Reply-To: <CALBAE1OSDeu39CQWvuxHhTYsBanMFhfLedf_oPf5z7px=jXhow@mail.gmail.com>
On 2/24/2022 8:35 PM, Jerin Jacob wrote:
> On Thu, Feb 24, 2022 at 4:13 PM Tomasz Duszynski <tduszynski@marvell.com> wrote:
>>
>> Add B0 variant to the list of supported models.
>>
>> Signed-off-by: Tomasz Duszynski <tduszynski@marvell.com>
>> Reviewed-by: Jerin Jacob Kollanukkaran <jerinj@marvell.com>
>
> Updated the git commit as follows and applied to
> dpdk-next-net-mrvl/for-next-net. Thanks
>
> common/cnxk: support CNF95xx B0 variant
>
> Add CNF95xx B0 variant to the list of supported models.
>
> Signed-off-by: Tomasz Duszynski <tduszynski@marvell.com>
> Reviewed-by: Jerin Jacob <jerinj@marvell.com>
>
>
>> drivers/common/cnxk/roc_model.c | 1 +
>> drivers/common/cnxk/roc_model.h | 6 ++++--
>> 2 files changed, 5 insertions(+), 2 deletions(-)
Hi Jerin, Tomasz,
Can you please update release note to document this new
device support? (Although it is still B0, some users may be
interested in with the new device support.)
next prev parent reply other threads:[~2022-02-25 10:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-24 10:42 Tomasz Duszynski
2022-02-24 20:35 ` Jerin Jacob
2022-02-25 10:03 ` Ferruh Yigit [this message]
2022-02-25 10:34 ` [dpdk-dev] [PATCH v2] common/cnxk: support CNF95xx " Tomasz Duszynski
2022-02-25 10:36 ` Jerin Jacob
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=e7e47277-e2fe-95e4-4e04-660b20db9b22@intel.com \
--to=ferruh.yigit@intel.com \
--cc=dev@dpdk.org \
--cc=jerinj@marvell.com \
--cc=jerinjacobk@gmail.com \
--cc=kirankumark@marvell.com \
--cc=ndabilpuram@marvell.com \
--cc=skori@marvell.com \
--cc=skoteshwar@marvell.com \
--cc=tduszynski@marvell.com \
--cc=thomas@monjalon.net \
/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).