From: Shiping Ji <shiping.linux@gmail.com>
To: Borislav Petkov <bp@alien8.de>, sashal@kernel.org
Cc: James Morse <james.morse@arm.com>,
robh+dt@kernel.org, mark.rutland@arm.com,
devicetree@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
linux-edac@vger.kernel.org,
Mauro Carvalho Chehab <mchehab@kernel.org>,
hangl@microsoft.com, Lei Wang <lewan@microsoft.com>,
shji@microsoft.com, ruizhao@microsoft.com,
Scott Branden <scott.branden@broadcom.com>,
Yuqing Shen <yuqing.shen@broadcom.com>,
ray.jui@broadcom.com, wangglei@gmail.com
Subject: Re: [PATCH v9 2/2] EDAC: add EDAC driver for DMC520
Date: Wed, 15 Jan 2020 13:49:56 -0800 [thread overview]
Message-ID: <3f1f28fd-2abf-2e1c-ef46-1992058b7a1a@gmail.com> (raw)
In-Reply-To: <20200115213848.GO20975@zn.tnic>
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@gmail.com>
>> Signed-off-by: Lei Wang <leiwang_git@outlook.com>
>> Reviewed-by: James Morse <james.morse@arm.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@outlook.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
next prev parent reply other threads:[~2020-01-15 21:49 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-15 14:32 [PATCH v9 2/2] EDAC: add EDAC driver for DMC520 Shiping Ji
2020-01-15 21:38 ` Borislav Petkov
2020-01-15 21:49 ` Shiping Ji [this message]
2020-01-15 22:05 ` Borislav Petkov
2020-01-15 22:08 ` Shiping Ji
2020-01-17 0:18 ` Borislav Petkov
2020-01-17 18:31 ` Shiping Ji
2020-01-17 18:40 ` Scott Branden
2020-01-17 18:57 ` Borislav Petkov
2020-01-17 0:31 ` Scott Branden
2020-01-17 18:24 ` Shiping Ji
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=3f1f28fd-2abf-2e1c-ef46-1992058b7a1a@gmail.com \
--to=shiping.linux@gmail.com \
--cc=bp@alien8.de \
--cc=devicetree@vger.kernel.org \
--cc=hangl@microsoft.com \
--cc=james.morse@arm.com \
--cc=lewan@microsoft.com \
--cc=linux-edac@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mchehab@kernel.org \
--cc=ray.jui@broadcom.com \
--cc=robh+dt@kernel.org \
--cc=ruizhao@microsoft.com \
--cc=sashal@kernel.org \
--cc=scott.branden@broadcom.com \
--cc=shji@microsoft.com \
--cc=wangglei@gmail.com \
--cc=yuqing.shen@broadcom.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).