From: Tomasz Duszynski <tdu@semihalf.com>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: Tomasz Duszynski <tdu@semihalf.com>,
dev@dpdk.org, pablo.de.lara.guarch@intel.com, dima@marvell.com,
Natalie Samsonov <nsamsono@marvell.com>
Subject: Re: [dpdk-dev] [PATCH] crypto/mrvl: rename PMD to mvsam
Date: Fri, 27 Apr 2018 07:31:11 +0200 [thread overview]
Message-ID: <20180427053111.GB7674@sh> (raw)
In-Reply-To: <20180426103812.5c406d35@xeon-e3>
On Thu, Apr 26, 2018 at 10:38:12AM -0700, Stephen Hemminger wrote:
> On Thu, 26 Apr 2018 19:22:00 +0200
> Tomasz Duszynski <tdu@semihalf.com> wrote:
>
> > Picking a company stock ticker for a PMD name might not be a best approach
> > in a long run since name is too generic.
> >
> > This patch addresses that and renames mrvl to mvsam.
> >
> > Signed-off-by: Natalie Samsonov <nsamsono@marvell.com>
> > Signed-off-by: Tomasz Duszynski <tdu@semihalf.com>
>
> I would prefer that the device name is the same as Linux or BSD.
> It makes life easier for multiple OS maintenance.
>
I understand your concern but since DPDK MRVL PMDs are based on external
MUSDK library, PMDs names are library centric, i.e we have mvpp2
NET PMD both in library (not prefixed) and in DPDK tree. Ideally the same
should apply to CRYPTO part and for the other future drivers as well.
--
- Tomasz Duszyński
next prev parent reply other threads:[~2018-04-27 5:31 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-26 17:22 Tomasz Duszynski
2018-04-26 17:38 ` Stephen Hemminger
2018-04-27 5:31 ` Tomasz Duszynski [this message]
2018-04-26 18:48 ` Thomas Monjalon
2018-04-27 5:18 ` Tomasz Duszynski
2018-04-27 7:15 ` [dpdk-dev] [PATCH v2] " Tomasz Duszynski
2018-05-07 14:19 ` De Lara Guarch, Pablo
2018-05-08 6:13 ` Tomasz Duszynski
2018-05-08 8:14 ` [dpdk-dev] [PATCH v3] " Tomasz Duszynski
2018-05-08 8:57 ` De Lara Guarch, Pablo
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=20180427053111.GB7674@sh \
--to=tdu@semihalf.com \
--cc=dev@dpdk.org \
--cc=dima@marvell.com \
--cc=nsamsono@marvell.com \
--cc=pablo.de.lara.guarch@intel.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).