From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: Jerin Jacob Kollanukkaran <jerinj@marvell.com>,
"dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH v2] net/octeontx: fix vdev name
Date: Wed, 20 Mar 2019 15:09:18 +0000 [thread overview]
Message-ID: <af9c00b8-5328-553d-2788-a58177594604@intel.com> (raw)
In-Reply-To: <20190319151910.220adfb7@shemminger-XPS-13-9360>
On 3/19/2019 10:19 PM, Stephen Hemminger wrote:
> On Tue, 19 Mar 2019 18:59:21 +0000
> Ferruh Yigit <ferruh.yigit@intel.com> wrote:
>
>> On 3/14/2019 3:35 PM, Jerin Jacob Kollanukkaran wrote:
>>> On Wed, 2019-03-13 at 14:58 -0700, Stephen Hemminger wrote:
>>>> The octeontx driver is creating vdev with name "OCTEONTX_PMD"
>>>> which is an artifact from how RTE_PMD_REGISTER_VDEV arguments
>>>> work.
>>>>
>>>> Change to use the same convention as all the other network
>>>> drivers ie "net_octeontx").
>>>>
>>>> Signed-off-by: Stephen Hemminger <stephen@networkplumber.org>
>>>> Reviewed-by: Ramil Rosen <ramirose@gmail.com>
>>>> ---
>>>
>>> Acked-by: Jerin Jacob <jerinj@marvell.com>
>>>
>>
>> Hi Jerin, Stephen,
>>
>> Can you please provide fixes line, (which commit broke the pmd name)?
>
> It goes all the way back to original submission:
>
> Fixes: f7be70e5130e ("net/octeontx: add net device probe and remove")
>
Indeed, I was assuming it has been broken somewhere on the way, but is seems no.
Applied to dpdk-next-net/master, thanks.
next prev parent reply other threads:[~2019-03-20 15:09 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-13 21:58 Stephen Hemminger
2019-03-13 21:58 ` Stephen Hemminger
2019-03-14 15:35 ` Jerin Jacob Kollanukkaran
2019-03-14 15:35 ` Jerin Jacob Kollanukkaran
2019-03-19 18:59 ` Ferruh Yigit
2019-03-19 18:59 ` Ferruh Yigit
2019-03-19 22:19 ` Stephen Hemminger
2019-03-19 22:19 ` Stephen Hemminger
2019-03-20 15:09 ` Ferruh Yigit [this message]
2019-03-20 15:09 ` 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=af9c00b8-5328-553d-2788-a58177594604@intel.com \
--to=ferruh.yigit@intel.com \
--cc=dev@dpdk.org \
--cc=jerinj@marvell.com \
--cc=stephen@networkplumber.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).