[GIT PULL] Basic StarFive JH7100 RISC-V SoC support for 5.17
Arnd Bergmann
arnd at arndb.de
Wed Dec 15 04:17:13 PST 2021
On Wed, Dec 15, 2021 at 12:25 PM Emil Renner Berthing <kernel at esmil.dk> wrote:
> On Tue, 14 Dec 2021 at 22:30, Arnd Bergmann <arnd at arndb.de> wrote:
> > On Sun, Nov 28, 2021 at 9:06 PM Emil Renner Berthing <kernel at esmil.dk> wrote:
> > I just got through my backlog of pull request and got to yours. All of
> > the contents look
> > fine but I noticed that there is no tag description. Please sign the
> > tag with a gpg
> > key and add a description that explains the contents of the branch in your own
> > words, the same way you write the introductory mail of a patch series. This will
> > become the description of the merge commit.
>
> Ah, gotcha. The thing is that I don't actually have a gpg key at the
> moment. I can generate one and use that to sign it, but then it won't
> be part of the web of trust.
> Alternatively I can just send it as a series of patches with a cover
> letter like I did before. That would be a little easier for me, but
> what do you prefer?
I'd prefer a pull request. The most important bit to me is actually the
tag description, not the signature. I'll go through the contents once
more anyway, which should be enough for me to merge it.
A signed tag is still better than one without a signature, that way at
least your key is part of the git history and we can confirm that another
pull request came was signed with the same key, even if we don't know
who you are ;-)
When you create a new key, please follow the directions from
https://www.kernel.org/doc/Documentation/process/maintainer-pgp-guide.rst
andyway, so you can add it to the keyring after you have collected the
signatures.
Arnd
More information about the linux-riscv
mailing list