From: Nikolay Borisov <nborisov@suse.com>
To: Qu Wenruo <wqu@suse.com>, linux-btrfs@vger.kernel.org
Subject: Re: [PATCH] btrfs: space-info: fix the wrong trace name for bytes_may_use
Date: Mon, 12 Oct 2020 15:08:05 +0300 [thread overview]
Message-ID: <018b567a-5671-4ace-7c63-e22e8546500c@suse.com> (raw)
In-Reply-To: <20201012065624.80649-1-wqu@suse.com>
On 12.10.20 г. 9:56 ч., Qu Wenruo wrote:
> The trace_name for bytes_may_use should be "may_use", "space_info".
>
> Fixes: f3e75e3805e1 ("btrfs: roll tracepoint into btrfs_space_info_update helper")
> Signed-off-by: Qu Wenruo <wqu@suse.com>
Reviewed-by: Nikolay Borisov <nborisov@suse.com>
next prev parent reply other threads:[~2020-10-12 12:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-12 6:56 [PATCH] btrfs: space-info: fix the wrong trace name for bytes_may_use Qu Wenruo
2020-10-12 12:08 ` Nikolay Borisov [this message]
2020-10-14 11:44 ` David Sterba
2020-10-14 11:59 ` Qu Wenruo
2020-10-22 13:35 ` David Sterba
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=018b567a-5671-4ace-7c63-e22e8546500c@suse.com \
--to=nborisov@suse.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=wqu@suse.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).