From: David Sterba <dsterba@suse.cz>
To: David Sterba <dsterba@suse.cz>
Cc: Lu Fengqi <lufq.fnst@cn.fujitsu.com>, linux-btrfs@vger.kernel.org
Subject: Re: [PATCH RESEND 0/4] fix alert and add testcase lowmem check
Date: Thu, 9 Nov 2017 17:25:41 +0100 [thread overview]
Message-ID: <20171109162540.GN27557@twin.jikos.cz> (raw)
In-Reply-To: <20171109162304.GM27557@twin.jikos.cz>
On Thu, Nov 09, 2017 at 05:23:04PM +0100, David Sterba wrote:
> On Fri, Nov 03, 2017 at 04:28:02PM +0800, Lu Fengqi wrote:
> > Patch 1 add a test case for commit 4c75ae7a4e20 ("btrfs-progs: test: Add
> > test image for lowmem mode file extent interrupt")
> > Patch 2 output more detailed information about file extent interrupt
> > Patch 3 fix a false alert for lowmem check
> > Patch 4 add a test case for Patch 3
> >
> > Lu Fengqi (4):
> > btrfs-progs: test: Add test image for lowmem mode file extent
> > interrupt
>
> I don't understand what 'interrupt' means in this context, it's been
> introduced in d88da10ddd4296cf2dd9 and I did not notice it at the time.
> The error message is unclear.
As this is only a minor issue, please send it as a followup patch,
patches 1-4 have been merged. Thanks.
prev parent reply other threads:[~2017-11-09 16:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-03 8:28 [PATCH RESEND 0/4] fix alert and add testcase lowmem check Lu Fengqi
2017-11-03 8:28 ` [PATCH RESEND 1/4] btrfs-progs: test: Add test image for lowmem mode file extent interrupt Lu Fengqi
2017-11-03 8:28 ` [PATCH RESEND 2/4] btrfs-progs: lowmem check: Output more detailed information about " Lu Fengqi
2017-11-03 8:28 ` [PATCH RESEND 3/4] btrfs-progs: lowmem check: Fix false alert about referencer count mismatch Lu Fengqi
2017-11-03 8:28 ` [PATCH RESEND 4/4] btrfs-progs: test: Add test image for lowmem mode referencer count mismatch false alert Lu Fengqi
2017-11-09 16:23 ` [PATCH RESEND 0/4] fix alert and add testcase lowmem check David Sterba
2017-11-09 16:25 ` 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=20171109162540.GN27557@twin.jikos.cz \
--to=dsterba@suse.cz \
--cc=linux-btrfs@vger.kernel.org \
--cc=lufq.fnst@cn.fujitsu.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).