From: Greg KH <greg@kroah.com>
To: Anand Jain <anand.jain@oracle.com>
Cc: linux-kernel@vger.kernel.org, stable@vger.kernel.org,
linux-btrfs@vger.kernel.org
Subject: Re: [PATCH 0/7] make btrfs/153 sucessful on 5.4.y
Date: Fri, 13 Aug 2021 12:18:27 +0200 [thread overview]
Message-ID: <YRZG81GsaIblr/II@kroah.com> (raw)
In-Reply-To: <cover.1628845854.git.anand.jain@oracle.com>
On Fri, Aug 13, 2021 at 05:55:23PM +0800, Anand Jain wrote:
> Patch 1-2 and 5 helps to fix the conflicts smoothly.
> Patch 3-4 and 6 fixes the regression as reported by the
> test case btrfs/153 and comes from the below patch-set
> (btrfs: qgroup: Fix the long-existing regression of btrfs/153)
> Patch 7 fixes lockdep Warning as in the commit log now reported by
> the test case btrfs/153 on 5.4.y
All queued up, thanks!
greg k-h
prev parent reply other threads:[~2021-08-13 10:19 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-13 9:55 [PATCH 0/7] make btrfs/153 sucessful on 5.4.y Anand Jain
2021-08-13 9:55 ` [PATCH 1/7] btrfs: make qgroup_free_reserved_data take btrfs_inode Anand Jain
2021-08-13 9:55 ` [PATCH 2/7] btrfs: make btrfs_qgroup_reserve_data " Anand Jain
2021-08-13 9:55 ` [PATCH 3/7] btrfs: qgroup: allow to unreserve range without releasing other ranges Anand Jain
2021-08-13 9:55 ` [PATCH 4/7] btrfs: qgroup: try to flush qgroup space when we get -EDQUOT Anand Jain
2021-08-13 10:26 ` Qu Wenruo
2021-08-13 10:30 ` Anand Jain
2021-08-13 10:39 ` Qu Wenruo
2021-08-13 10:41 ` Anand Jain
2021-08-13 10:56 ` Greg KH
2021-08-13 11:06 ` Anand Jain
2021-08-30 22:27 ` Anand Jain
2021-08-13 9:55 ` [PATCH 5/7] btrfs: transaction: Cleanup unused TRANS_STATE_BLOCKED Anand Jain
2021-08-13 9:55 ` [PATCH 6/7] btrfs: qgroup: remove ASYNC_COMMIT mechanism in favor of reserve retry-after-EDQUOT Anand Jain
2021-08-13 9:55 ` [PATCH 7/7] btrfs: fix lockdep splat when enabling and disabling qgroups Anand Jain
2021-08-13 10:18 ` Greg KH [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=YRZG81GsaIblr/II@kroah.com \
--to=greg@kroah.com \
--cc=anand.jain@oracle.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=stable@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.