From: Mimi Zohar <zohar@linux.ibm.com>
To: Petr Vorel <pvorel@suse.cz>, ltp@lists.linux.it
Cc: linux-integrity@vger.kernel.org, Alex Henrie <alexh@vpitech.com>,
alexhenrie24@gmail.com, Cyril Hrubis <chrubis@suse.cz>
Subject: Re: [PATCH 1/1] ima_measurements.sh: Use /proc/uptime instead of date
Date: Thu, 13 Jan 2022 20:11:45 -0500 [thread overview]
Message-ID: <8f0d69607590096c1be5d7c4c2a3ece316100ca0.camel@linux.ibm.com> (raw)
In-Reply-To: <20220112150123.13768-1-pvorel@suse.cz>
On Wed, 2022-01-12 at 16:01 +0100, Petr Vorel wrote:
> It fixes more iterations (e.g. -i2) which is more precise.
> date +%s could be used, but it's better use procfs file instead
> requiring binary.
>
> Signed-off-by: Petr Vorel <pvorel@suse.cz>
Thanks, Petr.
Reviewed-by: Mimi Zohar <zohar@linux.ibm.com>
next prev parent reply other threads:[~2022-01-14 1:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-12 15:01 [PATCH 1/1] ima_measurements.sh: Use /proc/uptime instead of date Petr Vorel
2022-01-14 1:11 ` Mimi Zohar [this message]
2022-01-14 8:53 ` Petr Vorel
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=8f0d69607590096c1be5d7c4c2a3ece316100ca0.camel@linux.ibm.com \
--to=zohar@linux.ibm.com \
--cc=alexh@vpitech.com \
--cc=alexhenrie24@gmail.com \
--cc=chrubis@suse.cz \
--cc=linux-integrity@vger.kernel.org \
--cc=ltp@lists.linux.it \
--cc=pvorel@suse.cz \
/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;
as well as URLs for NNTP newsgroup(s).