All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jarkko Sakkinen <jarkko@kernel.org>
To: Miguel Ojeda <miguel.ojeda.sandonis@gmail.com>
Cc: linux-kernel@vger.kernel.org, "Miguel Ojeda" <ojeda@kernel.org>,
	"Alex Gaynor" <alex.gaynor@gmail.com>,
	"Boqun Feng" <boqun.feng@gmail.com>,
	"Gary Guo" <gary@garyguo.net>,
	"Björn Roy Baron" <bjorn3_gh@protonmail.com>,
	"Benno Lossin" <benno.lossin@proton.me>,
	"Andreas Hindborg" <a.hindborg@kernel.org>,
	"Alice Ryhl" <aliceryhl@google.com>,
	"Trevor Gross" <tmgross@umich.edu>,
	rust-for-linux@vger.kernel.org, "Fiona Behrens" <me@kloenk.dev>,
	"Tamir Duberstein" <tamird@gmail.com>
Subject: Re: [PATCH] MAINTAINERS: TPM DEVICE DRIVER: linux-tpmdd-nixos
Date: Fri, 7 Mar 2025 18:52:41 +0200	[thread overview]
Message-ID: <Z8skWemfaM7siKl8@kernel.org> (raw)
In-Reply-To: <CANiq72kfo1zSsLc5TWr3wS3t2e5OK_hnECGMpAv-7ezyBsnPig@mail.gmail.com>

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).

> 
> Cheers,
> Miguel

BR, Jarkko

  reply	other threads:[~2025-03-07 16:52 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-06 21:17 [PATCH] MAINTAINERS: TPM DEVICE DRIVER: linux-tpmdd-nixos Jarkko Sakkinen
2025-03-06 21:19 ` Jarkko Sakkinen
2025-03-07  9:22 ` Miguel Ojeda
2025-03-07 16:52   ` Jarkko Sakkinen [this message]
2025-03-13 11:26     ` Fiona Behrens
2025-03-14 14:48       ` Jarkko Sakkinen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=Z8skWemfaM7siKl8@kernel.org \
    --to=jarkko@kernel.org \
    --cc=a.hindborg@kernel.org \
    --cc=alex.gaynor@gmail.com \
    --cc=aliceryhl@google.com \
    --cc=benno.lossin@proton.me \
    --cc=bjorn3_gh@protonmail.com \
    --cc=boqun.feng@gmail.com \
    --cc=gary@garyguo.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=me@kloenk.dev \
    --cc=miguel.ojeda.sandonis@gmail.com \
    --cc=ojeda@kernel.org \
    --cc=rust-for-linux@vger.kernel.org \
    --cc=tamird@gmail.com \
    --cc=tmgross@umich.edu \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.