From: Martin Wilck <martin.wilck@suse.com>
To: Shinichiro Kawasaki <shinichiro.kawasaki@wdc.com>,
Luis Chamberlain <mcgrof@kernel.org>
Cc: "linux-block@vger.kernel.org" <linux-block@vger.kernel.org>,
"patches@lists.linux.dev" <patches@lists.linux.dev>,
"gost.dev@samsung.com" <gost.dev@samsung.com>
Subject: Re: [PATCH blktests] nvme/053: provide time extension alternative
Date: Wed, 08 Jan 2025 21:12:32 +0100 [thread overview]
Message-ID: <6f46c75da6f865b04d3038cae8d3bfc6460ad02f.camel@suse.com> (raw)
In-Reply-To: <53p73kfx7akmecsc3sofrmga7o7m32gg2lp7e44nacxgwarfoo@u74aepo5erqs>
On Fri, 2024-12-20 at 11:37 +0000, Shinichiro Kawasaki wrote:
> On Dec 18, 2024 / 03:13, Luis Chamberlain wrote:
> > I get this failure when I run this test:
> >
> > awk: ...rescan.awk:2: warning: The time extension is obsolete.
> > Use the timex extension from gawkextlib
>
> get_sleep_time() {
> local duration=$((RANDOM % 50 + 1))
>
> echo "$((duration / 10))"."$((duration % 10))"
> }
>
> With this, we should be able to drop the awk script form the test
> case.
>
> Martin, what do you think?
Fine with me, and actually, nice. This way we don't need awk at all.
Do you want me to submit a patch, or will you do it yourself?
Martin
next prev parent reply other threads:[~2025-01-08 20:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-18 11:13 [PATCH blktests] nvme/053: provide time extension alternative Luis Chamberlain
2024-12-20 11:37 ` Shinichiro Kawasaki
2025-01-04 4:05 ` Luis Chamberlain
2025-01-08 20:12 ` Martin Wilck [this message]
2025-01-16 7:17 ` Shinichiro Kawasaki
2025-01-08 20:37 ` Martin Wilck
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=6f46c75da6f865b04d3038cae8d3bfc6460ad02f.camel@suse.com \
--to=martin.wilck@suse.com \
--cc=gost.dev@samsung.com \
--cc=linux-block@vger.kernel.org \
--cc=mcgrof@kernel.org \
--cc=patches@lists.linux.dev \
--cc=shinichiro.kawasaki@wdc.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;
as well as URLs for NNTP newsgroup(s).