[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20250319195818.GC126678@ziepe.ca>
Date: Wed, 19 Mar 2025 16:58:18 -0300
From: Jason Gunthorpe <jgg@...pe.ca>
To: Stefano Garzarella <sgarzare@...hat.com>
Cc: Jarkko Sakkinen <jarkko@...nel.org>, linux-integrity@...r.kernel.org,
linux-kernel@...r.kernel.org,
James Bottomley <James.Bottomley@...senpartnership.com>,
Peter Huewe <peterhuewe@....de>
Subject: Re: [RFC PATCH 3/3] tpm/tpm_svsm: use send_recv() op
On Tue, Mar 11, 2025 at 11:01:30AM +0100, Stefano Garzarella wrote:
> This driver does not support interrupts, and receiving the response is
> synchronous with sending the command.
>
> Let's simplify the driver by implementing the new send_recv() op.
>
> Signed-off-by: Stefano Garzarella <sgarzare@...hat.com>
> ---
> Note: this is based on "[PATCH v3 0/4] Enlightened vTPM support for SVSM
> on SEV-SNP" series [1].
> If we will merge this series before it, we can just ignore this patch
> and I'll squash these changes in that series.
>
> [1] https://lore.kernel.org/linux-integrity/20250311094225.35129-1-sgarzare@redhat.com/
> ---
> drivers/char/tpm/tpm_svsm.c | 46 ++++++++-----------------------------
> 1 file changed, 9 insertions(+), 37 deletions(-)
I think the diffstat speaks for itself, you should send this as
non-RFC
Jason
Powered by blists - more mailing lists