[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <D5AGGNMO6W6H.POLV23HA8CKQ@kernel.org>
Date: Fri, 01 Nov 2024 03:36:24 +0200
From: "Jarkko Sakkinen" <jarkko@...nel.org>
To: "Jarkko Sakkinen" <jarkko@...nel.org>, "Peter Huewe"
<peterhuewe@....de>, "Jason Gunthorpe" <jgg@...pe.ca>, "Jerry Snitselaar"
<jsnitsel@...hat.com>
Cc: <stable@...r.kernel.org>, "Mike Seo" <mikeseohyungjin@...il.com>, "open
list:TPM DEVICE DRIVER" <linux-integrity@...r.kernel.org>, "open list"
<linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v3] tpm: Lock TPM chip in tpm_pm_suspend() first
On Fri Nov 1, 2024 at 2:25 AM EET, Jarkko Sakkinen wrote:
> cmake -Bbuild -Dbuildroot_defconfig=busybox_x86_64_defconfig && make -Cbuild buildroot-prepare
> make -Cbuild/buildroot/build
> pushd build/buildroot/build
> images/run-qemu.sh &
> socat - UNIX-CONNECT:images/serial.sock
and export LINUX_OVERRIDE_SRCDIR=/home/jarkko/work/kernel.org/jarkko/linux-tpmdd
<offtopic>
I wondered what was the thing anyway with those "kernel patches for
Github/lab" discussed in LWN while ago. If you know how to propeerly
use BuildRoot, CI compatibility is and old thing. This has been fully
tested to run also inside CI (and has run-tests.sh based on TCL's
utility expect). How I understood that article was lack of knowledge
of the tools available. Hope none of those kernel patches never
landed tbh...
</offtopic>
BR, Jarkko
Powered by blists - more mailing lists