[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <eydewrcn4tviu6fbqmmvhoc2zao3uzrxwwlc55tuxuhfrexk5k@7xg5fdeu7wun>
Date: Thu, 24 Apr 2025 14:32:33 +0200
From: Uwe Kleine-König <ukleinek@...nel.org>
To: Alexey Charkov <alchark@...il.com>
Cc: Krzysztof Kozlowski <krzk@...nel.org>, Rob Herring <robh@...nel.org>,
Conor Dooley <conor+dt@...nel.org>, linux-arm-kernel@...ts.infradead.org, linux-pwm@...r.kernel.org,
devicetree@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2] dt-bindings: pwm: vt8500-pwm: Convert to YAML
Hello Alexey,
On Thu, Apr 24, 2025 at 12:07:03PM +0400, Alexey Charkov wrote:
> On Thu, Apr 24, 2025 at 10:35 AM Uwe Kleine-König <ukleinek@...nel.org> wrote:
> > I saw you signed your patch using PGP, which is great. However I didn't
> > find your key. I recommend to make it available on keys.openpgp.org like
> > this:
> >
> > gpg --export alchark@...il.com | curl -T - https://keys.openpgp.org
> >
> > and then verify your identities using the link in the output of this
> > command. Still better, (additionally) add your key to the kernel keyring
> > (which however requires you to be in Linus Torvalds WoT, see
> > https://korg.docs.kernel.org/pgpkeys.html for the details).
>
> Hmm, I used b4's built-in patatt functionality with a dedicated
> ed25519 key, not a gpg managed one. Looks like keys.openpgp.org
> doesn't understand those directly, or am I missing something?
No, I wasn't aware that patatt also uses signature algos other than PGP.
Without your key known, using ed25519 is kind of useless because it
cannot be verified. I would recommend switching to PGP because for that
the key distribution is a (somewhat) solved problem.
Nevertheless I'll play a bit with patatt and your key.
Best regards
Uwe
Download attachment "signature.asc" of type "application/pgp-signature" (489 bytes)
Powered by blists - more mailing lists