From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Amir Goldstein <amir73il@gmail.com>
Cc: Sasha Levin <sashal@kernel.org>,
"Darrick J . Wong" <djwong@kernel.org>,
Leah Rumancik <leah.rumancik@gmail.com>,
Chandan Babu R <chandan.babu@oracle.com>,
Luis Chamberlain <mcgrof@kernel.org>,
Adam Manzanares <a.manzanares@samsung.com>,
linux-xfs@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH 5.10 v2 0/6] xfs stable patches for 5.10.y (from v5.17)
Date: Thu, 25 Aug 2022 14:07:18 +0200 [thread overview]
Message-ID: <Ywdl9satF+g7dPhV@kroah.com> (raw)
In-Reply-To: <20220823121136.1806820-1-amir73il@gmail.com>
On Tue, Aug 23, 2022 at 03:11:30PM +0300, Amir Goldstein wrote:
> Hi Greg,
>
> This 5.10.y backport series contains fixes from v5.17 release.
>
> All the patches in this series have already been applied to 5.15.y
> except for patch 2 which you have queued to 5.15.y yesterday [1].
>
> Yesterday's 5.15.y series contains mostly fixed from v5.18/v5.19.
> The applicable fixed from that series will be included in the next
> 5.10.y series.
>
All now queued up, thanks.
greg k-h
prev parent reply other threads:[~2022-08-25 12:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-23 12:11 [PATCH 5.10 v2 0/6] xfs stable patches for 5.10.y (from v5.17) Amir Goldstein
2022-08-23 12:11 ` [PATCH 5.10 v2 1/6] xfs: prevent a WARN_ONCE() in xfs_ioc_attr_list() Amir Goldstein
2022-08-23 12:11 ` [PATCH 5.10 v2 2/6] xfs: reject crazy array sizes being fed to XFS_IOC_GETBMAP* Amir Goldstein
2022-08-23 12:11 ` [PATCH 5.10 v2 3/6] fs: remove __sync_filesystem Amir Goldstein
2022-08-23 12:11 ` [PATCH 5.10 v2 4/6] vfs: make sync_filesystem return errors from ->sync_fs Amir Goldstein
2022-08-23 12:11 ` [PATCH 5.10 v2 5/6] xfs: return errors in xfs_fs_sync_fs Amir Goldstein
2022-08-23 12:11 ` [PATCH 5.10 v2 6/6] xfs: only bother with sync_filesystem during readonly remount Amir Goldstein
2022-08-25 12:07 ` Greg Kroah-Hartman [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=Ywdl9satF+g7dPhV@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=a.manzanares@samsung.com \
--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 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.