Thread (57 messages) 57 messages, 4 authors, 2020-07-10

RE: [net-next v3 15/15] idpf: Introduce idpf driver

From: Kirsher, Jeffrey T <hidden>
Date: 2020-06-30 23:48:37

-----Original Message-----
From: Jakub Kicinski <kuba@kernel.org>
Sent: Friday, June 26, 2020 11:53
To: Kirsher, Jeffrey T <redacted>
Cc: davem@davemloft.net; Brady, Alan <redacted>;
netdev@vger.kernel.org; nhorman@redhat.com; sassmann@redhat.com;
Michael, Alice [off-list ref]; Burra, Phani R
[off-list ref]; Hay, Joshua A [off-list ref];
Chittim, Madhu [off-list ref]; Linga, Pavan Kumar
[off-list ref]; Skidmore, Donald C
[off-list ref]; Brandeburg, Jesse
[off-list ref]; Samudrala, Sridhar
[off-list ref]; lkp [off-list ref]
Subject: Re: [net-next v3 15/15] idpf: Introduce idpf driver

On Thu, 25 Jun 2020 19:07:37 -0700 Jeff Kirsher wrote:
quoted
+MODULE_AUTHOR("Intel Corporation, [off-list ref]");
Corporations do not author things, people do. Please drop this.
Your statement makes sense and I know that we have done this historically, like several other drivers (not saying it is right).  The thought process was that our drivers are not written by just one or two people, but more like 20+ developers.  So should we list all 20+ people that wrote the drivers, or just choose one person?  Also what happens when that person no longer works at Intel and the email is no longer vaild, should we constantly update the MODULE_AUTHOR() to reflect valid employees working on the driver?  That is the reason we were using "Intel Corporation" and a valid email that will always be good for support questions.
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help