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

[Jarkko Sakkinen <jarkko@kernel.org>]

On Thu, Mar 13, 2025 at 12:26:47PM +0100, Fiona Behrens wrote:
> Jarkko Sakkinen <jarkko@kernel.org> writes:
> 
> > 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@kernel.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).
> 
> Yeah exactly, took me a while to understand your usage :)
> I use nix mainly as a dev shell and plan to add building the kernel
> through nix.
> 
> Once I have the time and remember this still then I might try to include
> your work in the nix repo I maintain. Maybe we can also build docker
> container images for kernel development processes using nix and stuff
> like that.

Yes, so no plans to step on your toes. I'm going to keep this
"opionated repository" for my own maintainer work :-) And
possibly for some contributions outside my usual sandbox.

That said, anything can be taken for more generic use... [ping
me for license incompatibility issues, I de-facto to GPLv3 but
permit to other licensing framework on request].

> 
> Thanks,
> Fiona

BR, Jarkko