From: Mimi Zohar <zohar@linux.ibm.com>
To: Stefan Berger <stefanb@linux.ibm.com>, linux-integrity@vger.kernel.org
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] evm: Clean up some variables
Date: Mon, 16 May 2022 10:50:04 -0400 [thread overview]
Message-ID: <6d91e146702bcaf361cb193eaca35c57e38482df.camel@linux.ibm.com> (raw)
In-Reply-To: <20220513174105.3684229-1-stefanb@linux.ibm.com>
On Fri, 2022-05-13 at 13:41 -0400, Stefan Berger wrote:
> Make hmac_tfm static since it's not used anywhere else besides the file
> it is in.
>
> Remove declaration of hash_tfm since it doesn't exist.
>
> Signed-off-by: Stefan Berger <stefanb@linux.ibm.com>
Thanks, Stefan. Both this patch and "evm: Return INTEGRITY_PASS for
enum integrity_status value '0'" are now queued in next-integrity.
Mimi
next prev parent reply other threads:[~2022-05-16 14:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-13 17:41 [PATCH] evm: Clean up some variables Stefan Berger
2022-05-16 14:50 ` Mimi Zohar [this message]
2022-05-16 15:27 ` Stefan Berger
2022-05-16 22:50 ` Mimi Zohar
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=6d91e146702bcaf361cb193eaca35c57e38482df.camel@linux.ibm.com \
--to=zohar@linux.ibm.com \
--cc=linux-integrity@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=stefanb@linux.ibm.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox