linux-kernel - Re: [PATCH] MAINTAINERS: TPM DEVICE DRIVER: linux-tpmdd-nixos

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <Z8skWemfaM7siKl8@kernel.org>
Date: Fri, 7 Mar 2025 18:52:41 +0200
From: Jarkko Sakkinen <jarkko@...nel.org>
To: Miguel Ojeda <miguel.ojeda.sandonis@...il.com>
Cc: linux-kernel@...r.kernel.org, Miguel Ojeda <ojeda@...nel.org>,
	Alex Gaynor <alex.gaynor@...il.com>,
	Boqun Feng <boqun.feng@...il.com>, Gary Guo <gary@...yguo.net>,
	Björn Roy Baron <bjorn3_gh@...tonmail.com>,
	Benno Lossin <benno.lossin@...ton.me>,
	Andreas Hindborg <a.hindborg@...nel.org>,
	Alice Ryhl <aliceryhl@...gle.com>, Trevor Gross <tmgross@...ch.edu>,
	rust-for-linux@...r.kernel.org, Fiona Behrens <me@...enk.dev>,
	Tamir Duberstein <tamird@...il.com>
Subject: Re: [PATCH] MAINTAINERS: TPM DEVICE DRIVER: linux-tpmdd-nixos

On Fri, Mar 07, 2025 at 10:22:10AM +0100, Miguel Ojeda wrote:
> On Thu, Mar 6, 2025 at 10:17 PM Jarkko Sakkinen <jarkko@...nel.org> wrote:
> >
> > This is my new testing tree for my kernel tree. It will over time replace
> > my previous BuildRoot based testing tree (but not just yet).
> 
> Thanks for Cc'ing! I assume this is related to your subsystem and that
> it will go through there.
> 
> Cc'ing Fiona as well since she was interested in Nix and Tamir who
> does macOS; so they may be interested.

Yeah, so I just used get_maintainer.pl and it picked you but I'm
happy if you enjoy it :-) linux-tpmdd comes originally from TPM driver
but these days it's really just my maintainer tree for every possible
pull request I do, as I'm also e.g. Linux keyring co-maintainer.

My biggest barrier with Rust has been testing (like almost always in any
software engineering problem) so I just figured out something that would
sort it out for me. I also thought that by starting doing some testing
for Rust patch sets that contain some tests would be a low-barrier way
for me to learn a bit how everything works in that side.

I think I quickly talked about this with Fiona and this is a bit
different angle in a way i.e., using Nix for profit as a tool to
implement together with Docker a trivial embedded build system so that
you can build kernel + EFI in any operating system (I personally use
Fedora).

> 
> Cheers,
> Miguel

BR, Jarkko