From: Raslan Darawsheh <rasland@nvidia.com>
To: "NBU-Contact-Thomas Monjalon (EXTERNAL)" <thomas@monjalon.net>,
"ajit.khaparde@broadcom.com" <ajit.khaparde@broadcom.com>,
Andrew Rybchenko <andrew.rybchenko@oktetlabs.ru>,
"jerinj@marvell.com" <jerinj@marvell.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
"ferruh.yigit@intel.com" <ferruh.yigit@intel.com>,
"Gal Cohen (ProdM)" <galco@nvidia.com>
Subject: RE: [PATCH] devtools: add E-Switch keyword for commit checks
Date: Thu, 24 Feb 2022 11:07:47 +0000 [thread overview]
Message-ID: <BYAPR12MB3078EEB706CA4E755396DEAECF3D9@BYAPR12MB3078.namprd12.prod.outlook.com> (raw)
In-Reply-To: <5243139.Sb9uPGUboI@thomas>
++ adding more people here,
> -----Original Message-----
> From: Thomas Monjalon <thomas@monjalon.net>
> Sent: Thursday, February 24, 2022 11:36 AM
> To: Raslan Darawsheh <rasland@nvidia.com>
> Cc: dev@dpdk.org; ferruh.yigit@intel.com; Gal Cohen (ProdM)
> <galco@nvidia.com>
> Subject: Re: [PATCH] devtools: add E-Switch keyword for commit checks
>
> 24/02/2022 10:26, Raslan Darawsheh:
> > This adds the syntax for E-Switch to have check on how it suppose to
> > be for commits
> [...]
> > +E-Switch
>
> It looks Mellanox people use this syntax in Linux kernel as well.
> Where does it come from? Is it a Mellanox-only wording?
>
I don't think it's a Mellanox only wording see the following:
https://www.kernel.org/doc/html/latest/networking/devlink/devlink-port.html?#devlink-port
https://www.kernel.org/doc/html/latest/networking/switchdev.html
> Intuitively, I would have written it eSwitch generally.
I would go with E-Switch
> It means "embedded switch", right?
In kernel, it's Ethernet Switch device.
https://www.kernel.org/doc/html/latest/networking/switchdev.html
>
>
Kindest regards,
Raslan Darawsheh
next prev parent reply other threads:[~2022-02-24 11:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-24 9:26 Raslan Darawsheh
2022-02-24 9:35 ` Thomas Monjalon
2022-02-24 11:07 ` Raslan Darawsheh [this message]
2022-02-24 19:20 ` Ajit Khaparde
2023-03-28 18:43 ` Thomas Monjalon
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=BYAPR12MB3078EEB706CA4E755396DEAECF3D9@BYAPR12MB3078.namprd12.prod.outlook.com \
--to=rasland@nvidia.com \
--cc=ajit.khaparde@broadcom.com \
--cc=andrew.rybchenko@oktetlabs.ru \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=galco@nvidia.com \
--cc=jerinj@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).