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 stable-5.15.y 0/4] backport test case btrfs/216 fixes
Date: Fri, 17 Dec 2021 15:56:21 +0100 [thread overview]
Message-ID: <YbylFav0uyKztfKX@kroah.com> (raw)
In-Reply-To: <cover.1639658429.git.anand.jain@oracle.com>
On Thu, Dec 16, 2021 at 09:04:09PM +0800, Anand Jain wrote:
> In an attempt to make all the fstests test cases pass on stable-5.15.y,
> backport fixes for the test case btrfs/216.
>
> Anand Jain (4):
> btrfs: convert latest_bdev type to btrfs_device and rename
> btrfs: use latest_dev in btrfs_show_devname
> btrfs: update latest_dev when we create a sprout device
> btrfs: remove stale comment about the btrfs_show_devname
>
> fs/btrfs/disk-io.c | 6 +++---
> fs/btrfs/extent_io.c | 2 +-
> fs/btrfs/inode.c | 2 +-
> fs/btrfs/super.c | 26 ++++++--------------------
> fs/btrfs/volumes.c | 19 +++++++------------
> fs/btrfs/volumes.h | 6 +++++-
> 6 files changed, 23 insertions(+), 38 deletions(-)
>
> --
> 2.33.1
>
Now queued up, thanks.
greg k-h
prev parent reply other threads:[~2021-12-17 14:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-16 13:04 [PATCH stable-5.15.y 0/4] backport test case btrfs/216 fixes Anand Jain
2021-12-16 13:04 ` [PATCH stable-5.15.y 1/4] btrfs: convert latest_bdev type to btrfs_device and rename Anand Jain
2021-12-16 13:04 ` [PATCH stable-5.15.y 2/4] btrfs: use latest_dev in btrfs_show_devname Anand Jain
2021-12-16 13:04 ` [PATCH stable-5.15.y 3/4] btrfs: update latest_dev when we create a sprout device Anand Jain
2021-12-16 13:04 ` [PATCH stable-5.15.y 4/4] btrfs: remove stale comment about the btrfs_show_devname Anand Jain
2021-12-17 14:56 ` 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=YbylFav0uyKztfKX@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox