Re: [PATCH] drivers: pwm: replace `kernel::c_str!` with C-Strings

[Uwe Kleine-König]

On Tue, Jan 20, 2026 at 11:15:56AM -0500, Tamir Duberstein wrote:
> On Tue, Jan 20, 2026 at 3:39 AM Uwe Kleine-König <ukleinek@xxxxxxxxxx> wrote:
> > (Side note, b4 told me:
> >
> >           ✗ No key: openssh/tamird@xxxxxxxxx
> >
> > . It's not clear to me how to verify this signature. My experiments
> > include:
> >
> >         $ b4 kr --show-keys 20251222-cstr-pwm-v1-1-e8916d976f8d@xxxxxxxxx
> >         ---
> >         No keys found in the thread.
> >
> > and looking at
> > https://lore.kernel.org/linux-pwm/20251222-cstr-pwm-v1-1-e8916d976f8d@xxxxxxxxx/raw
> > where I see
> >
> >         X-Developer-Key: i=tamird@xxxxxxxxx; a=openssh; fpr=SHA256:264rPmnnrb+ERkS7DDS3tuwqcJss/zevJRzoylqMsbc
> >
> > which IIUC isn't enough to verify the next mail signed with the same
> > key. Am I missing something? I very appreciate signing your work, but if
> > there is no way for me (or anyone else) to verify it, there is no gain.)
> 
> Yep, you are right to call this out. My usual setup uses SSH keys for
> commit signing, which are not part of the kernel web of trust. I
> promise to start signing kernel work with my GPG key soon :)

While I notice that the trend goes to using ssh-keys, I still prefer
OpenPGP. So +1 on your plan.
 
> In the meantime if you trust Github you can verify my signature
> against https://github.com/tamird.keys.

OK, for the record:

	$ curl --create-dirs -o ~/.local/share/b4/keyring/openssh/gmail.com/tamird/default https://github.com/tamird.keys

makes `b4 am
CAJ-ks9=USrGECVS1qMqs+iCKUqvOdfcjA6phAjaF0wfcTkQt_g@xxxxxxxxxxxxxx`
emit:

	  ✓ Signed: openssh/tamird@xxxxxxxxx (From: tamird@xxxxxxxxxx)

This looks a bit strange (because there is gmail and kernel.org), but
better than before.

Best regards
Uwe

Attachment: signature.asc
Description: PGP signature