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 v3 0/5] xfs stable patches for 5.10.y (from v5.18+)
Date: Fri, 2 Sep 2022 08:17:10 +0200 [thread overview]
Message-ID: <YxGf5gGWItX7tp4M@kroah.com> (raw)
In-Reply-To: <20220901133356.2473299-1-amir73il@gmail.com>
On Thu, Sep 01, 2022 at 04:33:51PM +0300, Amir Goldstein wrote:
> Hi Greg,
>
> This 5.10.y backport series contains fixes from v5.18 and v5.19-rc1.
>
> The patches in this series have already been applied to 5.15.y in Leah's
> latest update [1], so this 5.10.y is is mostly catching up with 5.15.y.
Now queued up, thanks.
greg k-h
prev parent reply other threads:[~2022-09-02 6:17 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-01 13:33 [PATCH 5.10 v3 0/5] xfs stable patches for 5.10.y (from v5.18+) Amir Goldstein
2022-09-01 13:33 ` [PATCH 5.10 v3 1/5] xfs: remove infinite loop when reserving free block pool Amir Goldstein
2022-09-02 6:16 ` Greg Kroah-Hartman
2022-09-02 7:04 ` Amir Goldstein
2022-09-01 13:33 ` [PATCH 5.10 v3 2/5] xfs: always succeed at setting the reserve pool size Amir Goldstein
2022-09-01 13:33 ` [PATCH 5.10 v3 3/5] xfs: fix overfilling of reserve pool Amir Goldstein
2022-09-01 13:33 ` [PATCH 5.10 v3 4/5] xfs: fix soft lockup via spinning in filestream ag selection loop Amir Goldstein
2022-09-01 13:33 ` [PATCH 5.10 v3 5/5] xfs: revert "xfs: actually bump warning counts when we send warnings" Amir Goldstein
2022-09-02 6:17 ` 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=YxGf5gGWItX7tp4M@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox