All of lore.kernel.org
 help / color / mirror / Atom feed
From: Shiping Ji <shiping.linux@gmail.com>
To: Borislav Petkov <bp@alien8.de>
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>,
	Mauro Carvalho Chehab <mchehab@kernel.org>,
	linux-edac@vger.kernel.org, sashal@kernel.org,
	hangl@microsoft.com, Lei Wang <lewan@microsoft.com>,
	ruizhao@microsoft.com, Scott Branden <scott.branden@broadcom.com>,
	Yuqing Shen <yuqing.shen@broadcom.com>,
	ray.jui@broadcom.com, wangglei@gmail.com, shji@microsoft.com
Subject: Re: [PATCH v8 2/2] EDAC: add EDAC driver for DMC520
Date: Wed, 15 Jan 2020 06:22:48 -0800	[thread overview]
Message-ID: <78dc4c79-985f-32b9-c8c4-a38aeb64b49d@gmail.com> (raw)
In-Reply-To: <20200115124833.GE20975@zn.tnic>

On 1/15/2020 4:48 AM, Borislav Petkov wrote:
> On Tue, Jan 14, 2020 at 03:52:23PM -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>
>> Reviewed-by: James Morse <james.morse@arm.com>
> 
> I don't think you've understood the whole SOB chain thing yet. Previous
> submissions had
> 
> Signed-off-by: Lei Wang <leiwang_git@outlook.com>
> 
> and her as author and you've completely removed those and made yourself
> an author because when I apply this patch, it would take the From:
> header from the mail and make it the author.
> 
> But you can't simply remove her authorship... you need to read that doc
> again.
> 

Sorry about it, my misunderstanding again. I'll submit a new patch shortly.

-- 
Best regards,
Shiping Ji

      reply	other threads:[~2020-01-15 14:22 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-14 23:52 [PATCH v8 2/2] EDAC: add EDAC driver for DMC520 Shiping Ji
2020-01-15 12:48 ` Borislav Petkov
2020-01-15 14:22   ` Shiping Ji [this message]

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=78dc4c79-985f-32b9-c8c4-a38aeb64b49d@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.