From: Michael Ellerman <mpe@ellerman.id.au>
To: Stephen Rothwell <sfr@canb.auug.org.au>,
PowerPC <linuxppc-dev@lists.ozlabs.org>
Cc: Paul Mackerras <paulus@ozlabs.org>,
Nicholas Piggin <npiggin@gmail.com>,
Fabiano Rosas <farosas@linux.ibm.com>,
Suraj Jitindar Singh <sjitindarsingh@gmail.com>,
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 powerpc tree
Date: Thu, 24 Jun 2021 17:42:50 +1000 [thread overview]
Message-ID: <878s2z1zet.fsf@mpe.ellerman.id.au> (raw)
In-Reply-To: <20210622074622.4e483a33@canb.auug.org.au>
Stephen Rothwell <sfr@canb.auug.org.au> writes:
> Hi all,
>
> Commit
>
> 77bbbc0cf848 ("KVM: PPC: Book3S HV: Fix TLB management on SMT8 POWER9 and POWER10 processors")
>
> is missing a Signed-off-by from its author.
That was actually deliberate.
Suraj wrote the patch when he was at IBM, but never sent it.
Paul & Nick then resurrected it from some internal tree, and are now
submitting it on behalf of IBM.
So they are asserting option b) of the DCO AIUI:
(b) The contribution is based upon previous work that, to the best
of my knowledge, is covered under an appropriate open source
license and I have the right under that license to submit that
work with modifications, whether created in whole or in part
by me, under the same open source license (unless I am
permitted to submit under a different license), as indicated
in the file
cheers
next prev parent reply other threads:[~2021-06-24 7:42 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-21 21:46 linux-next: Signed-off-by missing for commit in the powerpc tree Stephen Rothwell
2021-06-24 7:42 ` Michael Ellerman [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
2022-05-19 22:31 Stephen Rothwell
2022-05-20 5:20 ` Nicholas Piggin
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=878s2z1zet.fsf@mpe.ellerman.id.au \
--to=mpe@ellerman.id.au \
--cc=farosas@linux.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=npiggin@gmail.com \
--cc=paulus@ozlabs.org \
--cc=sfr@canb.auug.org.au \
--cc=sjitindarsingh@gmail.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 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).