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: <3f1f28fd-2abf-2e1c-ef46-1992058b7a1a@gmail.com>
Date:   Wed, 15 Jan 2020 13:49:56 -0800
From:   Shiping Ji <shiping.linux@...il.com>
To:     Borislav Petkov <bp@...en8.de>, sashal@...nel.org
Cc:     James Morse <james.morse@....com>, robh+dt@...nel.org,
        mark.rutland@....com, devicetree@...r.kernel.org,
        LKML <linux-kernel@...r.kernel.org>, linux-edac@...r.kernel.org,
        Mauro Carvalho Chehab <mchehab@...nel.org>,
        hangl@...rosoft.com, Lei Wang <lewan@...rosoft.com>,
        shji@...rosoft.com, ruizhao@...rosoft.com,
        Scott Branden <scott.branden@...adcom.com>,
        Yuqing Shen <yuqing.shen@...adcom.com>, ray.jui@...adcom.com,
        wangglei@...il.com
Subject: Re: [PATCH v9 2/2] EDAC: add EDAC driver for DMC520

On 1/15/2020 1:38 PM, Borislav Petkov wrote:
> On Wed, Jan 15, 2020 at 06:32:33AM -0800, Shiping Ji wrote:
>> New driver supports error detection and correction on the devices with ARM
>> DMC-520 memory controller.
>>
>> Signed-off-by: Shiping Ji <shiping.linux@...il.com>
>> Signed-off-by: Lei Wang <leiwang_git@...look.com>
>> Reviewed-by: James Morse <james.morse@....com>
> 
> This mail still has your From: because I guess you pasted the patch in
> the mail.
> 
> But, if you look at what I wrote here:
> 
> https://lkml.kernel.org/r/20200107195606.GM29542@zn.tnic
> 
> you'll see the
> 
> From: Lei Wang <leiwang_git@...look.com>
> 
> which is the last From: in the mail and that is taken by git as the
> author of the patch.
> 
> However, if I apply this mail of yours, it will make you the
> author. Because in git there can be only one author per patch
> and other authors can be additionally accredited with the
> Co-developed-by: tag from the same doc I was pointing at before:
> Documentation/process/submitting-patches.rst
>
> Looking at this driver, however, you have supplied three authors. And I
> think you guys need to discuss it amongst yourselves who is going to be
> the author of this driver in the git history.

Lei will be the author of this driver in the git history. I could ask her to send the patch again if that's the correct way to go. Please confirm.
 
> If there are more questions, I'm pretty sure Sasha would be glad to
> explain to you how the whole authorship thing works and what the
> implications are.

Thanks, Sasha is currently OOF until April 19th. 

--
Best regards,
Shiping Ji

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ