public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Ard Biesheuvel" <ard.biesheuvel@linaro.org>
To: Leif Lindholm <leif.lindholm@linaro.org>
Cc: "Philippe Mathieu-Daudé" <philmd@redhat.com>,
	edk2-devel-groups-io <devel@edk2.groups.io>,
	"Pete Batard" <pete@akeo.ie>,
	samer.el-haj-mahmoud@arm.com, "Laszlo Ersek" <lersek@redhat.com>
Subject: Re: [edk2-platforms][PATCH v2 3/7] Platform/RPi: Replace Bcm283x SoC base register address with a PCD
Date: Tue, 19 Nov 2019 13:51:33 +0100	[thread overview]
Message-ID: <CAKv+Gu-_4rf1sbDF6bkk2iV45xAcSv=av4xq3XLKdyVMjh-OUg@mail.gmail.com> (raw)
In-Reply-To: <20191119124434.GB7323@bivouac.eciton.net>

On Tue, 19 Nov 2019 at 13:44, Leif Lindholm <leif.lindholm@linaro.org> wrote:
>
> On Tue, Nov 19, 2019 at 01:16:28PM +0100, Philippe Mathieu-Daudé wrote:
> > > As per Leif's comments in
> > > https://www.mail-archive.com/devel@edk2.groups.io/msg05292.html:
> > >
> > > "I don't want patches submitted with anyone other than the
> > > contributor's Signed-off-by"
> >
> > I missed this thread, now I'm slightly confused.
> >
> > Checking the Wiki:
> >
> > https://github.com/tianocore/edk2/blob/master/Readme.md#code-contributions
> >
> > and:
> >
> > https://github.com/tianocore/tianocore.github.io/wiki/Commit-Signature-Format#signed-off-by
> >
> > Signed-off-by
> >
> >     Authors should use Signed-off-by (See example below)
> >     If you've received the code from a trusted source, and are
> >     forwarding it along, please add a Signed-off-by line for
> >     yourself to indicate that you know this code to be usable
> >     by our community.
> >
> > The guideline is simply "add a S-o-b", but Leif says "[only?]
>
> No.
> Whoever contributes the patch must add an S-o-b.
> And contracts are signed in one's own name.
>
> This is not a TianoCore twitch, this is the fundamental way in which
> DCO works in all projects that use it - including linux and QEMU.
>
> https://wiki.qemu.org/Contribute/SubmitAPatch:
> * You must provide a Signed-off-by: line (this is a hard requirement
>   because it's how you say "I'm legally okay to contribute this and
>   happy for it to go into QEMU"
> which is based on
> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/process/submitting-patches.rst?h=v5.4-rc8#n418
>
> The confusing bit I find here is in
> https://wiki.qemu.org/Contribute/SubmitAPatch#Patch_emails_must_include_a_Signed-off-by:_line
> with its statement of "but again, that author's Signed-off-by: line is
> mandatory,", in direct conflict with the text at the top of the page
> *if* the patch was not one already contributed to QEMU.
>

The point is really that you should not add a s-o-b line just to
credit authorship. The s-o-b indicates that the person in question
asserts that the contribution is compatible with the project's license
policies. The author may not even be aware that the code is being
contributed to a certain project, and so adding a s-o-b on their
behalf in this case should be avoided. TL;DR: SOB != authorship

It might make sense to permit an Author: or Authored-by: tag to make
this distinction more explicit.

  reply	other threads:[~2019-11-19 12:51 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-19 11:38 [edk2-platforms][PATCH v2 0/7] Platform/RPi: Early Raspberry Pi 4 groundwork Pete Batard
2019-11-19 11:38 ` [edk2-platforms][PATCH v2 1/7] Platform/RPi: Add missing model name Pete Batard
2019-11-19 12:02   ` Philippe Mathieu-Daudé
2019-11-19 12:14     ` [edk2-devel] " Leif Lindholm
2019-11-19 12:25       ` Philippe Mathieu-Daudé
2019-11-19 12:50         ` Leif Lindholm
2019-11-19 12:25     ` Pete Batard
2019-11-19 11:38 ` [edk2-platforms][PATCH v2 2/7] Platform/RPi: Add model family detection Pete Batard
2019-11-19 11:38 ` [edk2-platforms][PATCH v2 3/7] Platform/RPi: Replace Bcm283x SoC base register address with a PCD Pete Batard
2019-11-19 11:43   ` Philippe Mathieu-Daudé
2019-11-19 11:57     ` Pete Batard
2019-11-19 12:16       ` Philippe Mathieu-Daudé
2019-11-19 12:44         ` Leif Lindholm
2019-11-19 12:51           ` Ard Biesheuvel [this message]
2019-11-19 11:38 ` [edk2-platforms][PATCH v2 4/7] Platform/RPi: Use offsets for Bcm238x SoC register addresses Pete Batard
2019-11-19 11:46   ` Philippe Mathieu-Daudé
2019-11-19 11:38 ` [edk2-platforms][PATCH v2 5/7] Silicon/Broadcom: Add Bcm2711 header Pete Batard
2019-11-19 11:51   ` Philippe Mathieu-Daudé
2019-11-19 11:38 ` [edk2-platforms][PATCH v2 6/7] Platform/RPi: Read more variables from VideoCore during early init Pete Batard
2019-11-19 11:38 ` [edk2-platforms][PATCH v2 7/7] Platform/RPi: Clean up and improve early memory init Pete Batard
2019-11-19 18:20 ` [edk2-platforms][PATCH v2 0/7] Platform/RPi: Early Raspberry Pi 4 groundwork Leif Lindholm

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-list 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='CAKv+Gu-_4rf1sbDF6bkk2iV45xAcSv=av4xq3XLKdyVMjh-OUg@mail.gmail.com' \
    --to=devel@edk2.groups.io \
    /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