From: "Philippe Mathieu-Daudé" <philmd@redhat.com>
To: devel@edk2.groups.io, leif.lindholm@linaro.org
Cc: Pete Batard <pete@akeo.ie>,
ard.biesheuvel@linaro.org, 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:16:28 +0100 [thread overview]
Message-ID: <87a12ccb-0441-72dd-875f-840b0a2a2861@redhat.com> (raw)
In-Reply-To: <1ae9ef75-aecb-e71c-c1b5-ce9f5d99c5a0@akeo.ie>
On 11/19/19 12:57 PM, Pete Batard wrote:
> On 2019.11.19 11:43, Philippe Mathieu-Daudé wrote:
>> On 11/19/19 12:38 PM, Pete Batard wrote:
>>> From: Samer El-Haj-Mahmoud <samer.el-haj-mahmoud@arm.com>
>>>
>>> Define BCM2836_SOC_REGISTERS from PcdBcm283xRegistersAddress. This is
>>> needed in preparation for adding Raspberry Pi 4 support, since the two
>>> Pi's have a different base addresses for the Bcm283x specific registers.
>>>
>>
>> Shouldn't this patch also include Samer's S-o-b tag?
>
> I think we went over this already (but I can't seem to find that e-mail
> from the list).
>
> 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?] If patches
are modified after contribution, but before being pushed, then then
additional contributions can be reflected with additional
Signed-off-bys." and then "I don't want patches submitted with anyone
other than the contributor's Signed-off-by:".
Leif, can we clarify and update the documentation accordingly?
Sorry to be picky, but that would clear any confusion.
Thanks,
Phil.
next prev parent reply other threads:[~2019-11-19 12:16 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é [this message]
2019-11-19 12:44 ` Leif Lindholm
2019-11-19 12:51 ` Ard Biesheuvel
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=87a12ccb-0441-72dd-875f-840b0a2a2861@redhat.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