From: Nicholas Piggin <npiggin@gmail.com>
To: Michael Ellerman <mpe@ellerman.id.au>,
Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
PowerPC <linuxppc-dev@lists.ozlabs.org>
Subject: Re: linux-next: Signed-off-by missing for commit in the powerpc tree
Date: Fri, 20 May 2022 15:20:12 +1000 [thread overview]
Message-ID: <1653023904.pbe3pabbua.astroid@bobo.none> (raw)
In-Reply-To: <20220520083150.57e953fc@canb.auug.org.au>
Excerpts from Stephen Rothwell's message of May 20, 2022 8:31 am:
> Hi all,
>
> Commits
>
> 03a2e65f54b3 ("KVM: PPC: Book3S Nested: Use explicit 4096 LPID maximum")
> 18827eeef022 ("KVM: PPC: Remove kvmppc_claim_lpid")
>
> are missing a Signed-off-by from their authors.
Sorry.
> The first is just "Signed-of-by" misspelling. The second is missing.
My laptop's 'f' key has got much worse since then :(
Thanks,
Nick
next prev parent reply other threads:[~2022-05-20 5:20 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-19 22:31 linux-next: Signed-off-by missing for commit in the powerpc tree Stephen Rothwell
2022-05-20 5:20 ` Nicholas Piggin [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-10-23 21:16 Stephen Rothwell
2023-10-24 3:57 ` Michael Ellerman
2021-06-21 21:46 Stephen Rothwell
2021-06-24 7:42 ` Michael Ellerman
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
2018-06-03 18:26 Stephen Rothwell
2018-06-04 10:39 ` Michael Ellerman
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=1653023904.pbe3pabbua.astroid@bobo.none \
--to=npiggin@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.au \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).