From: David Sterba <dsterba@suse.cz>
To: David Sterba <dsterba@suse.cz>
Cc: Qu Wenruo <wqu@suse.com>, linux-btrfs@vger.kernel.org
Subject: Re: [PATCH 0/2] btrfs-progs: small compile warning fixes
Date: Wed, 26 Aug 2020 17:43:16 +0200 [thread overview]
Message-ID: <20200826154316.GI28318@twin.jikos.cz> (raw)
In-Reply-To: <20200826153112.GH28318@twin.jikos.cz>
On Wed, Aug 26, 2020 at 05:31:12PM +0200, David Sterba wrote:
> On Wed, Aug 26, 2020 at 08:47:32AM +0800, Qu Wenruo wrote:
> > Although the global parameter fs_info would affect all repair tests...
>
> Can you please be more specific?
Ok I see, fsck/013-extent-tree-rebuild test fails.
prev parent reply other threads:[~2020-08-26 15:44 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-26 0:47 [PATCH 0/2] btrfs-progs: small compile warning fixes Qu Wenruo
2020-08-26 0:47 ` [PATCH 1/2] btrfs-progs: fix compile warning due to global fs_info cleanup Qu Wenruo
2020-08-26 14:26 ` Josef Bacik
2020-08-28 16:06 ` David Sterba
2020-08-26 0:47 ` [PATCH 2/2] btrfs-progs: remove the unused variable in check_chunks_and_extents_lowmem() Qu Wenruo
2020-08-26 14:29 ` Josef Bacik
2020-08-28 16:06 ` David Sterba
2020-08-26 15:31 ` [PATCH 0/2] btrfs-progs: small compile warning fixes David Sterba
2020-08-26 15:43 ` David Sterba [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=20200826154316.GI28318@twin.jikos.cz \
--to=dsterba@suse.cz \
--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