From: David Sterba <dsterba@suse.cz>
To: Anand Jain <anand.jain@oracle.com>
Cc: linux-btrfs@vger.kernel.org, dsterba@suse.com, josef@toxicpanda.com
Subject: Re: [PATCH] btrfs: fixup read_policy latency
Date: Fri, 8 Jan 2021 14:57:19 +0100 [thread overview]
Message-ID: <20210108135719.GW6430@twin.jikos.cz> (raw)
In-Reply-To: <e9cd491fb05be97dbba756b7d0b9df3418b02a1d.1609916374.git.anand.jain@oracle.com>
On Wed, Jan 06, 2021 at 03:08:15PM +0800, Anand Jain wrote:
> In the meantime, since I have sent the base patch as below [1], the
> block layer commit 0d02129e76ed (block: merge struct block_device and
> struct hd_struct) has changed the first argument in the function
> part_stat_read_all() to struct block_device in 5.11-rc1. So the
> compilation will fail. This patch fixes it.
>
> This fixup patch must be rolled into its base patch [1].
> [1] [PATCH v2 1/4] btrfs: add read_policy latency
>
> I will include these changes in the base patch after the review comments.
It would be better to resend the patchset in this case as the fixup is
not just cosmetic. So far there's no discussion ongoing so resend would
not break the flow.
next prev parent reply other threads:[~2021-01-08 13:59 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-29 7:54 [PATCH v2 0/4] btrfs: read_policy types latency, device and round-robin Anand Jain
2020-10-29 7:54 ` [PATCH v2 1/4] btrfs: add read_policy latency Anand Jain
2021-01-06 7:08 ` [PATCH] btrfs: fixup " Anand Jain
2021-01-08 13:57 ` David Sterba [this message]
2021-01-11 9:55 ` Anand Jain
2020-10-29 7:54 ` [PATCH v2 2/4] btrfs: introduce new device-state read_preferred Anand Jain
2020-10-29 7:54 ` [PATCH 3/4] btrfs: introduce new read_policy device Anand Jain
2020-10-29 7:54 ` [PATCH RFC 4/4] btrfs: introduce new read_policy round-robin 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=20210108135719.GW6430@twin.jikos.cz \
--to=dsterba@suse.cz \
--cc=anand.jain@oracle.com \
--cc=dsterba@suse.com \
--cc=josef@toxicpanda.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