[PATCH] drivers: pwm: replace `kernel::c_str!` with C-Strings
Tamir Duberstein
tamird at kernel.org
Tue Jan 20 08:15:56 PST 2026
On Tue, Jan 20, 2026 at 3:39 AM Uwe Kleine-König <ukleinek at kernel.org> wrote:
>
> Hello,
>
> On Mon, Dec 22, 2025 at 01:24:46PM +0100, Tamir Duberstein wrote:
> > From: Tamir Duberstein <tamird at gmail.com>
> >
> > C-String literals were added in Rust 1.77. Replace instances of
> > `kernel::c_str!` with C-String literals where possible.
> >
> > Signed-off-by: Tamir Duberstein <tamird at gmail.com>
>
> Applied to
>
> https://git.kernel.org/pub/scm/linux/kernel/git/ukleinek/linux.git pwm/for-next
>
> as merge window material with the R-b tags by Michal Wilczynski and
> Daniel Almeida.
>
> (Side note, b4 told me:
>
> ✗ No key: openssh/tamird at gmail.com
>
> . It's not clear to me how to verify this signature. My experiments
> include:
>
> $ b4 kr --show-keys 20251222-cstr-pwm-v1-1-e8916d976f8d at gmail.com
> ---
> No keys found in the thread.
>
> and looking at
> https://lore.kernel.org/linux-pwm/20251222-cstr-pwm-v1-1-e8916d976f8d@gmail.com/raw
> where I see
>
> X-Developer-Key: i=tamird at gmail.com; 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 :)
In the meantime if you trust Github you can verify my signature
against https://github.com/tamird.keys.
Cheers.
Tamir
More information about the linux-riscv
mailing list