All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andre Przywara <andre.przywara@arm.com>
To: Catalin Marinas <catalin.marinas@arm.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
	Will Deacon <will@kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: Signed-off-by missing for commit in the arm64 tree
Date: Wed, 24 Mar 2021 16:45:51 +0000	[thread overview]
Message-ID: <20210324164551.7fedf89c@slackpad.fritz.box> (raw)
In-Reply-To: <20210324154613.GA3709@arm.com>

On Wed, 24 Mar 2021 15:46:14 +0000
Catalin Marinas <catalin.marinas@arm.com> wrote:

> On Wed, Mar 24, 2021 at 08:14:45AM +1100, Stephen Rothwell wrote:
> > Commits
> > 
> >   b17f265bb4cc ("kselftest/arm64: mte: Fix MTE feature detection")
> >   4dfc9d30a8ab ("kselftest/arm64: mte: common: Fix write() warnings")
> > 
> > are missing a Signed-off-by from their author.  
> 
> Thanks Stephen. Now fixed.

Thanks Catalin, and apologies for the blunder, that's what I get from
trying multitasking with just a single X chromosome ;-)

Cheers,
Andre

  reply	other threads:[~2021-03-24 16:47 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-23 21:14 linux-next: Signed-off-by missing for commit in the arm64 tree Stephen Rothwell
2021-03-24 15:46 ` Catalin Marinas
2021-03-24 16:45   ` Andre Przywara [this message]
  -- strict thread matches above, loose matches on Subject: below --
2025-05-21 11:39 Stephen Rothwell
2025-05-21 11:56 ` Rob Herring
2025-05-22 10:21   ` Will Deacon
2022-09-06 17:31 Stephen Rothwell
2022-09-06 22:01 ` Mark Brown
2022-07-20 13:12 Stephen Rothwell
2022-03-08 21:17 Stephen Rothwell
2020-09-29  9:51 Stephen Rothwell
2017-11-07  5:31 Stephen Rothwell
2017-11-13 15:44 ` Will Deacon

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=20210324164551.7fedf89c@slackpad.fritz.box \
    --to=andre.przywara@arm.com \
    --cc=catalin.marinas@arm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    --cc=will@kernel.org \
    /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.