From: Leon Romanovsky <leon@kernel.org>
To: Sunil Kovvuri <sunil.kovvuri@gmail.com>
Cc: Jakub Kicinski <kuba@kernel.org>,
Linux Netdev List <netdev@vger.kernel.org>,
"David S. Miller" <davem@davemloft.net>,
Tomasz Duszynski <tduszynski@marvell.com>,
Subbaraya Sundeep <sbhatta@marvell.com>,
Geetha sowjanya <gakula@marvell.com>,
Sunil Goutham <sgoutham@marvell.com>
Subject: Re: [PATCH net-next 3/6] octeontx2-vf: Virtual function driver dupport
Date: Wed, 11 Mar 2020 12:16:46 +0200 [thread overview]
Message-ID: <20200311101646.GJ4215@unreal> (raw)
In-Reply-To: <CA+sq2Ce7OFeKXBc_hHWODGuhgfNmfhOanhW4uyr=GLxAwZUPKw@mail.gmail.com>
On Wed, Mar 11, 2020 at 12:44:00PM +0530, Sunil Kovvuri wrote:
> On Wed, Mar 11, 2020 at 3:13 AM Jakub Kicinski <kuba@kernel.org> wrote:
> >
> > On Wed, 11 Mar 2020 00:17:22 +0530 sunil.kovvuri@gmail.com wrote:
> > > +#define DRV_NAME "octeontx2-nicvf"
> > > +#define DRV_STRING "Marvell OcteonTX2 NIC Virtual Function Driver"
> > > +#define DRV_VERSION "1.0"
> >
> > Please drop the driver version, kernel version should be used upstream.
> >
>
> Okay, will do.
>
> > > +
> > > +static const struct pci_device_id otx2_vf_id_table[] = {
> > > + { PCI_DEVICE(PCI_VENDOR_ID_CAVIUM, PCI_DEVID_OCTEONTX2_RVU_AFVF) },
> > > + { PCI_DEVICE(PCI_VENDOR_ID_CAVIUM, PCI_DEVID_OCTEONTX2_RVU_VF) },
> > > + { }
> > > +};
> > > +
> > > +MODULE_AUTHOR("Marvell International Ltd.");
> >
> > Only people can be authors, please put your name here or remove this.
> >
>
> Just for my understanding, is this due to a decision taken in netdev recently ?
> I have searched through all drivers in netdev and there is a mix of
> organizations and individuals as AUTHORS.
> Here we used org name to avoid specifying multiple names.
It was always the case in all subsystems. The authorship belongs to the developer
and not to the company. In opposite to the copyright.
Thanks
next prev parent reply other threads:[~2020-03-11 10:16 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-10 18:47 [PATCH net-next 0/6] octeontx2-vf: Add network driver for virtual function sunil.kovvuri
2020-03-10 18:47 ` [PATCH net-next 1/6] octeontx2-pf: Enable SRIOV and added VF mbox handling sunil.kovvuri
2020-03-10 21:43 ` Jakub Kicinski
2020-03-10 18:47 ` [PATCH net-next 2/6] octeontx2-pf: Handle VF function level reset sunil.kovvuri
2020-03-10 21:43 ` Jakub Kicinski
2020-03-10 18:47 ` [PATCH net-next 3/6] octeontx2-vf: Virtual function driver dupport sunil.kovvuri
2020-03-10 21:43 ` Jakub Kicinski
2020-03-11 7:14 ` Sunil Kovvuri
2020-03-11 10:16 ` Leon Romanovsky [this message]
2020-03-11 21:24 ` Jakub Kicinski
2020-03-10 18:47 ` [PATCH net-next 4/6] octeontx2-vf: Ethtool support sunil.kovvuri
2020-03-10 19:21 ` Andrew Lunn
2020-03-11 6:39 ` Sunil Kovvuri
2020-03-11 7:05 ` Leon Romanovsky
2020-03-11 7:18 ` Sunil Kovvuri
2020-03-11 10:12 ` Leon Romanovsky
2020-03-10 21:45 ` Jakub Kicinski
2020-03-11 6:40 ` Sunil Kovvuri
2020-03-10 18:47 ` [PATCH net-next 5/6] octeontx2-vf: Link event notification support sunil.kovvuri
2020-03-10 18:47 ` [PATCH net-next 6/6] octeontx2-pf: Cleanup all receive buffers in SG descriptor sunil.kovvuri
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=20200311101646.GJ4215@unreal \
--to=leon@kernel.org \
--cc=davem@davemloft.net \
--cc=gakula@marvell.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=sbhatta@marvell.com \
--cc=sgoutham@marvell.com \
--cc=sunil.kovvuri@gmail.com \
--cc=tduszynski@marvell.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).