All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael Ellerman <mpe@ellerman.id.au>
To: Stephen Rothwell <sfr@canb.auug.org.au>,
	Benjamin Herrenschmidt <benh@kernel.crashing.org>,
	PowerPC <linuxppc-dev@lists.ozlabs.org>
Cc: Linux-Next Mailing List <linux-next@vger.kernel.org>,
	"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
	Michal Suchanek <msuchanek@suse.de>
Subject: Re: linux-next: Signed-off-by missing for commit in the powerpc tree
Date: Mon, 04 Jun 2018 20:39:54 +1000	[thread overview]
Message-ID: <87in6ybzt1.fsf@concordia.ellerman.id.au> (raw)
In-Reply-To: <20180604042626.286a9469@canb.auug.org.au>

Stephen Rothwell <sfr@canb.auug.org.au> writes:

> Hi all,
>
> Commit
>
>   cb3d6759a93c ("powerpc/64s: Enable barrier_nospec based on firmware settings")
>
> is missing a Signed-off-by from its author.

Sorry my fault.

cheers

  reply	other threads:[~2018-06-04 10:40 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-03 18:26 linux-next: Signed-off-by missing for commit in the powerpc tree Stephen Rothwell
2018-06-04 10:39 ` Michael Ellerman [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-10-23 21:16 Stephen Rothwell
2023-10-23 21:16 ` Stephen Rothwell
2023-10-24  3:57 ` Michael Ellerman
2023-10-24  3:57   ` Michael Ellerman
2022-05-19 22:31 Stephen Rothwell
2022-05-19 22:31 ` Stephen Rothwell
2022-05-20  5:20 ` Nicholas Piggin
2022-05-20  5:20   ` Nicholas Piggin
2021-06-21 21:46 Stephen Rothwell
2021-06-21 21:46 ` Stephen Rothwell
2021-06-24  7:42 ` Michael Ellerman
2021-06-24  7:42   ` Michael Ellerman
2019-05-06 20:35 Stephen Rothwell
2019-05-06 20:35 ` Stephen Rothwell
2019-02-23 14:05 Stephen Rothwell
2019-02-24 11:48 ` Michael Ellerman
2019-02-24 22:47   ` Stephen Rothwell
2019-02-24 22:47     ` Stephen Rothwell
2017-11-14 20:26 Stephen Rothwell
2017-11-15 10:11 ` Michael Ellerman

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=87in6ybzt1.fsf@concordia.ellerman.id.au \
    --to=mpe@ellerman.id.au \
    --cc=benh@kernel.crashing.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=msuchanek@suse.de \
    --cc=sfr@canb.auug.org.au \
    /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.