From: Greg KH <gregkh@linuxfoundation.org>
To: Chandan Babu R <chandan.babu@oracle.com>
Cc: sashal@kernel.org, mcgrof@kernel.org, linux-xfs@vger.kernel.org,
stable@vger.kernel.org, djwong@kernel.org, amir73il@gmail.com,
leah.rumancik@gmail.com
Subject: Re: [PATCH 5.4 0/6] xfs stable candidate patches for 5.4.y (from v5.9)
Date: Fri, 11 Nov 2022 10:04:59 +0100 [thread overview]
Message-ID: <Y24QOy837I6eLxkT@kroah.com> (raw)
In-Reply-To: <20221111041025.87704-1-chandan.babu@oracle.com>
On Fri, Nov 11, 2022 at 09:40:19AM +0530, Chandan Babu R wrote:
> Hi Greg,
>
> This 5.4.y backport series contains XFS fixes from v5.9. The patchset
> has been acked by Darrick.
>
Now queued up, thanks.
greg k-h
prev parent reply other threads:[~2022-11-11 9:05 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-11 4:10 [PATCH 5.4 0/6] xfs stable candidate patches for 5.4.y (from v5.9) Chandan Babu R
2022-11-11 4:10 ` [PATCH 5.4 1/6] xfs: preserve rmapbt swapext block reservation from freed blocks Chandan Babu R
2022-11-11 4:10 ` [PATCH 5.4 2/6] xfs: rename xfs_bmap_is_real_extent to is_written_extent Chandan Babu R
2022-11-11 4:10 ` [PATCH 5.4 3/6] xfs: redesign the reflink remap loop to fix blkres depletion crash Chandan Babu R
2022-11-21 9:55 ` [PATCH 5.4 V2] " Chandan Babu R
2022-11-21 12:13 ` Greg KH
2022-11-11 4:10 ` [PATCH 5.4 4/6] xfs: use MMAPLOCK around filemap_map_pages() Chandan Babu R
2022-11-11 4:10 ` [PATCH 5.4 5/6] xfs: preserve inode versioning across remounts Chandan Babu R
2022-11-11 4:10 ` [PATCH 5.4 6/6] xfs: drain the buf delwri queue before xfsaild idles Chandan Babu R
2022-11-11 9:04 ` 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=Y24QOy837I6eLxkT@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=amir73il@gmail.com \
--cc=chandan.babu@oracle.com \
--cc=djwong@kernel.org \
--cc=leah.rumancik@gmail.com \
--cc=linux-xfs@vger.kernel.org \
--cc=mcgrof@kernel.org \
--cc=sashal@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