From: Jarkko Sakkinen <jarkko@kernel.org>
To: Shuah Khan <skhan@linuxfoundation.org>
Cc: linux-kselftest@vger.kernel.org, Shuah Khan <shuah@kernel.org>,
linux-integrity@vger.kernel.org, rust-for-linux@vger.kernel.org
Subject: Re: kselftest and cargo
Date: Thu, 18 Sep 2025 19:35:43 +0300 [thread overview]
Message-ID: <aMw032Im4D9zy77g@kernel.org> (raw)
In-Reply-To: <6712e20a-0fa9-44f5-ae0d-f4d9c3324028@linuxfoundation.org>
On Thu, Sep 18, 2025 at 10:04:13AM -0600, Shuah Khan wrote:
> On 9/18/25 09:15, Jarkko Sakkinen wrote:
> > On Thu, Sep 18, 2025 at 06:06:31PM +0300, Jarkko Sakkinen wrote:
> > > On Tue, Sep 16, 2025 at 04:39:37PM -0600, Shuah Khan wrote:
> > > > On 9/16/25 07:48, Jarkko Sakkinen wrote:
> > > > > Hi,
> > > > >
> > > > > The pre-existing kselftest for TPM2 is derived works of my earlier Python
> > > > > based rudimentary TPM2 stack called 'tpm2-scripts'.
> > > > >
> > > > > In order to get more coverage and more mainintainable and extensible test
> > > > > suite I'd like to eventually rewrite the tests with bash and tpm2sh, which
> > > > > is a TPM2 cli written with Rust and based on my new TPM2 stack [1] [2].
> > > > >
> > > > > Given linux-rust work, would it be acceptable to require cargo to install
> > > > > a runner for kselftest?
>
> What is runner for kselftest in this context?
It would really just a bash commanding tpm2sh and with conditional
check the binding is kept loose.
BR, Jarkko
prev parent reply other threads:[~2025-09-18 16:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-16 13:48 kselftest and cargo Jarkko Sakkinen
2025-09-16 13:52 ` Jarkko Sakkinen
2025-09-16 22:39 ` Shuah Khan
2025-09-18 15:06 ` Jarkko Sakkinen
2025-09-18 15:15 ` Jarkko Sakkinen
2025-09-18 16:04 ` Shuah Khan
2025-09-18 16:35 ` Jarkko Sakkinen [this message]
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=aMw032Im4D9zy77g@kernel.org \
--to=jarkko@kernel.org \
--cc=linux-integrity@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=rust-for-linux@vger.kernel.org \
--cc=shuah@kernel.org \
--cc=skhan@linuxfoundation.org \
/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.