From: Pavel Reichl <preichl@redhat.com>
To: Wang Yugui <wangyugui@e16-tech.com>, fstests@vger.kernel.org
Subject: Re: [PATCH] fstests: add missing _require_scratch
Date: Fri, 19 Aug 2022 12:36:02 +0200 [thread overview]
Message-ID: <de7b86fd-4228-60ef-01ee-3ff44ba9debe@redhat.com> (raw)
In-Reply-To: <20220818025614.47274-1-wangyugui@e16-tech.com>
Looks good to me.
Reviewed-by: Pavel Reichl <preichl@redhat.com>
prev parent reply other threads:[~2022-08-19 10:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-18 2:56 [PATCH] fstests: add missing _require_scratch Wang Yugui
2022-08-19 10:36 ` Pavel Reichl [this message]
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=de7b86fd-4228-60ef-01ee-3ff44ba9debe@redhat.com \
--to=preichl@redhat.com \
--cc=fstests@vger.kernel.org \
--cc=wangyugui@e16-tech.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