From: Johannes Thumshirn <Johannes.Thumshirn@wdc.com>
To: "fdmanana@kernel.org" <fdmanana@kernel.org>,
"linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>
Subject: Re: [PATCH] Btrfs: always copy scrub arguments back to user space
Date: Thu, 16 Jan 2020 11:59:26 +0000 [thread overview]
Message-ID: <43D93D40-9A62-465F-A880-0D7758FF63CB@wdc.com> (raw)
In-Reply-To: <20200116112920.30400-1-fdmanana@kernel.org>
Looks good,
Reviewed-by: Johannes Thumshirn <johannes.thumshirn@wdc.com>
next prev parent reply other threads:[~2020-01-16 11:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-16 11:29 [PATCH] Btrfs: always copy scrub arguments back to user space fdmanana
2020-01-16 11:59 ` Johannes Thumshirn [this message]
2020-01-16 12:00 ` Qu Wenruo
2020-01-16 14:12 ` David Sterba
2020-01-17 14:24 ` Graham Cobb
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=43D93D40-9A62-465F-A880-0D7758FF63CB@wdc.com \
--to=johannes.thumshirn@wdc.com \
--cc=fdmanana@kernel.org \
--cc=linux-btrfs@vger.kernel.org \
/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).