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  PHC 
Open Source and information security mailing list archives
Hash Suite for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:   Tue, 30 Jun 2020 17:59:23 -0700
From:   Jakub Kicinski <>
To:     "Kirsher, Jeffrey T" <>
Cc:     "" <>,
        "Brady, Alan" <>,
        "" <>,
        "" <>,
        "" <>,
        "Michael, Alice" <>,
        "Burra, Phani R" <>,
        "Hay, Joshua A" <>,
        "Chittim, Madhu" <>,
        "Linga, Pavan Kumar" <>,
        "Skidmore, Donald C" <>,
        "Brandeburg, Jesse" <>,
        "Samudrala, Sridhar" <>,
        lkp <>
Subject: Re: [net-next v3 15/15] idpf: Introduce idpf driver

On Tue, 30 Jun 2020 23:48:34 +0000 Kirsher, Jeffrey T wrote:
> > On Thu, 25 Jun 2020 19:07:37 -0700 Jeff Kirsher wrote:  
> > > +MODULE_AUTHOR("Intel Corporation, <>");  
> > 
> > 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.

MODULE_AUTHOR() is not required, most of the "documentation" page for
this driver is about where to get support, MAINTAINERS exist..  not to
mention that this is an upstream driver, so posting to netdev is always

I think we should be covered.

Powered by blists - more mailing lists