All of lore.kernel.org
 help / color / mirror / Atom feed
From: Catalin Marinas <catalin.marinas@arm.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Will Deacon <will.deacon@arm.com>,
	Linux Next Mailing List <linux-next@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	"Okamoto, Takayuki" <tokamoto@jp.fujitsu.com>,
	Zhang Lei <zhang.lei@jp.fujitsu.com>,
	Mark Rutland <mark.rutland@arm.com>
Subject: Re: linux-next: Signed-off-by missing for commit in the arm64-fixes tree
Date: Tue, 19 Mar 2019 14:51:11 +0000	[thread overview]
Message-ID: <20190319145111.GH59586@arrakis.emea.arm.com> (raw)
In-Reply-To: <20190320014312.562c8f6d@canb.auug.org.au>

Hi Stephen,

On Wed, Mar 20, 2019 at 01:43:12AM +1100, Stephen Rothwell wrote:
> Commit
> 
>   a4d17a19c493 ("arm64: apply workaround on A64FX v1r0")
> 
> is missing a Signed-off-by from its author.

Thanks for this. The patch is indeed confusing, sent by Takayuki with a
signed-off-by from Zhang and re-written by Mark while keeping the
original text.

I'm going to make Mark the author while keeping Takayuki as reported-by.

-- 
Catalin

  reply	other threads:[~2019-03-19 14:51 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-19 14:43 linux-next: Signed-off-by missing for commit in the arm64-fixes tree Stephen Rothwell
2019-03-19 14:51 ` Catalin Marinas [this message]
  -- strict thread matches above, loose matches on Subject: below --
2019-08-01 13:56 Stephen Rothwell
2019-08-01 14:10 ` Will Deacon
2019-08-01 14:25   ` Stephen Rothwell
2021-01-14 19:24 Stephen Rothwell
2021-01-15  9:22 ` Catalin Marinas

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=20190319145111.GH59586@arrakis.emea.arm.com \
    --to=catalin.marinas@arm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=sfr@canb.auug.org.au \
    --cc=tokamoto@jp.fujitsu.com \
    --cc=will.deacon@arm.com \
    --cc=zhang.lei@jp.fujitsu.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.