From: David Sterba <dsterba@suse.cz>
To: Liu Bo <bo.li.liu@oracle.com>
Cc: linux-btrfs@vger.kernel.org, clm@fb.com
Subject: Re: [PATCH] Btrfs: fix comp_oper to get right order
Date: Fri, 13 Mar 2015 13:37:34 +0100 [thread overview]
Message-ID: <20150313123734.GI20767@twin.jikos.cz> (raw)
In-Reply-To: <1426227878-29928-1-git-send-email-bo.li.liu@oracle.com>
On Fri, Mar 13, 2015 at 02:24:38PM +0800, Liu Bo wrote:
> Case (oper1->seq > oper2->seq) should differ with case (oper1->seq < oper2->seq).
>
> Signed-off-by: Liu Bo <bo.li.liu@oracle.com>
Reviewed-by: David Sterba <dsterba@suse.cz>
and should go to stable@ if not to 4.1-rc as it's a bug in the core of
qgroups. Waiting for the next merge window would not buy us anything.
> ---
> This typo was hiden in a big patch, so we need to work harder on review.
Of course, lack of reviews that come from non-maintainers is a perpetual
problem. There are never too many and each is highly appreciated.
next prev parent reply other threads:[~2015-03-13 12:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-13 6:24 [PATCH] Btrfs: fix comp_oper to get right order Liu Bo
2015-03-13 12:37 ` David Sterba [this message]
2015-03-13 18:27 ` Filipe David Manana
2015-03-13 19:07 ` Filipe David Manana
2015-03-13 22:22 ` 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=20150313123734.GI20767@twin.jikos.cz \
--to=dsterba@suse.cz \
--cc=bo.li.liu@oracle.com \
--cc=clm@fb.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