Linux-EDAC Archive on
 help / color / Atom feed
From: Borislav Petkov <>
To: Shiping Ji <>,
Cc: James Morse <>,,,, LKML <>,,
	Mauro Carvalho Chehab <>,, Lei Wang <>,,,
	Scott Branden <>,
	Yuqing Shen <>,,
Subject: Re: [PATCH v9 2/2] EDAC: add EDAC driver for DMC520
Date: Wed, 15 Jan 2020 22:38:48 +0100
Message-ID: <20200115213848.GO20975@zn.tnic> (raw)
In-Reply-To: <>

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 <>
> Signed-off-by: Lei Wang <>
> Reviewed-by: James Morse <>

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:

you'll see the

From: Lei Wang <>

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:

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.

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.



  reply index

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-15 14:32 Shiping Ji
2020-01-15 21:38 ` Borislav Petkov [this message]
2020-01-15 21:49   ` Shiping Ji
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 publically 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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20200115213848.GO20975@zn.tnic \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

Linux-EDAC Archive on

Archives are clonable:
	git clone --mirror linux-edac/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 linux-edac linux-edac/ \
	public-inbox-index linux-edac

Example config snippet for mirrors

Newsgroup available over NNTP:

AGPL code for this site: git clone