lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <61CC2BC414934749BD9F5BF3D5D9404498743241@ORSMSX112.amr.corp.intel.com>
Date:   Tue, 30 Jun 2020 23:48:34 +0000
From:   "Kirsher, Jeffrey T" <jeffrey.t.kirsher@...el.com>
To:     Jakub Kicinski <kuba@...nel.org>
CC:     "davem@...emloft.net" <davem@...emloft.net>,
        "Brady, Alan" <alan.brady@...el.com>,
        "netdev@...r.kernel.org" <netdev@...r.kernel.org>,
        "nhorman@...hat.com" <nhorman@...hat.com>,
        "sassmann@...hat.com" <sassmann@...hat.com>,
        "Michael, Alice" <alice.michael@...el.com>,
        "Burra, Phani R" <phani.r.burra@...el.com>,
        "Hay, Joshua A" <joshua.a.hay@...el.com>,
        "Chittim, Madhu" <madhu.chittim@...el.com>,
        "Linga, Pavan Kumar" <pavan.kumar.linga@...el.com>,
        "Skidmore, Donald C" <donald.c.skidmore@...el.com>,
        "Brandeburg, Jesse" <jesse.brandeburg@...el.com>,
        "Samudrala, Sridhar" <sridhar.samudrala@...el.com>,
        lkp <lkp@...el.com>
Subject: RE: [net-next v3 15/15] idpf: Introduce idpf driver

> -----Original Message-----
> From: Jakub Kicinski <kuba@...nel.org>
> Sent: Friday, June 26, 2020 11:53
> To: Kirsher, Jeffrey T <jeffrey.t.kirsher@...el.com>
> Cc: davem@...emloft.net; Brady, Alan <alan.brady@...el.com>;
> netdev@...r.kernel.org; nhorman@...hat.com; sassmann@...hat.com;
> Michael, Alice <alice.michael@...el.com>; Burra, Phani R
> <phani.r.burra@...el.com>; Hay, Joshua A <joshua.a.hay@...el.com>;
> Chittim, Madhu <madhu.chittim@...el.com>; Linga, Pavan Kumar
> <pavan.kumar.linga@...el.com>; Skidmore, Donald C
> <donald.c.skidmore@...el.com>; Brandeburg, Jesse
> <jesse.brandeburg@...el.com>; Samudrala, Sridhar
> <sridhar.samudrala@...el.com>; lkp <lkp@...el.com>
> Subject: Re: [net-next v3 15/15] idpf: Introduce idpf driver
> 
> On Thu, 25 Jun 2020 19:07:37 -0700 Jeff Kirsher wrote:
> > +MODULE_AUTHOR("Intel Corporation, <linux.nics@...el.com>");
> 
> 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.

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ