From: Josef Bacik <josef@toxicpanda.com>
To: Anand Jain <anand.jain@oracle.com>, linux-btrfs@vger.kernel.org
Cc: dsterba@suse.com
Subject: Re: [PATCH v9 0/3] readmirror feature (read_policy sysfs and in-memory only approach)
Date: Mon, 26 Oct 2020 10:01:41 -0400 [thread overview]
Message-ID: <4fb5fc91-d2b6-1732-d6a1-193d4bd7e59d@toxicpanda.com> (raw)
In-Reply-To: <cover.1603347462.git.anand.jain@oracle.com>
On 10/22/20 3:43 AM, Anand Jain wrote:
> v9: C coding style fixes in 1/3 and 3/3
>
You can add
Reviewed-by: Josef Bacik <josef@toxicpanda.com>
to this series, lets get this in so we can focus on the actual changes to the
policy. Thanks,
Josef
next prev parent reply other threads:[~2020-10-26 14:01 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-22 7:43 [PATCH v9 0/3] readmirror feature (read_policy sysfs and in-memory only approach) Anand Jain
2020-10-22 7:43 ` [PATCH v9 1/3] btrfs: add btrfs_strmatch helper Anand Jain
2020-10-23 11:12 ` Christoph Hellwig
2020-10-27 13:25 ` Anand Jain
2020-10-26 17:52 ` David Sterba
2020-10-27 13:19 ` Anand Jain
2020-10-27 18:00 ` David Sterba
2020-10-22 7:43 ` [PATCH v9 2/3] btrfs: create read policy framework Anand Jain
2020-10-22 7:43 ` [PATCH v9 3/3] btrfs: create read policy sysfs attribute, pid Anand Jain
2020-10-26 17:57 ` David Sterba
2020-10-28 12:37 ` Anand Jain
2020-10-23 17:04 ` [PATCH v9 0/3] readmirror feature (read_policy sysfs and in-memory only approach) David Sterba
2020-10-27 1:52 ` Anand Jain
2020-10-27 18:02 ` David Sterba
2020-10-28 12:06 ` Anand Jain
2020-10-26 14:01 ` Josef Bacik [this message]
2020-10-28 4:25 ` [PATCH v10 " Anand Jain
2020-10-28 4:25 ` [PATCH v10 1/3] btrfs: add btrfs_strmatch helper Anand Jain
2020-10-28 4:25 ` [PATCH v10 2/3] btrfs: create read policy framework Anand Jain
2020-10-28 4:25 ` [PATCH v10 3/3] btrfs: create read policy sysfs attribute, pid Anand Jain
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=4fb5fc91-d2b6-1732-d6a1-193d4bd7e59d@toxicpanda.com \
--to=josef@toxicpanda.com \
--cc=anand.jain@oracle.com \
--cc=dsterba@suse.com \
--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