From: Greg KH <gregkh@linuxfoundation.org>
To: Leah Rumancik <leah.rumancik@gmail.com>
Cc: stable@vger.kernel.org, linux-xfs@vger.kernel.org, amir73il@gmail.com
Subject: Re: [PATCH 5.15 v2 0/6] xfs stable candidate patches for 5.15.y (part 3)
Date: Sat, 23 Jul 2022 17:25:06 +0200 [thread overview]
Message-ID: <YtwS0l617OyO9Hop@kroah.com> (raw)
In-Reply-To: <20220721213610.2794134-1-leah.rumancik@gmail.com>
On Thu, Jul 21, 2022 at 02:36:04PM -0700, Leah Rumancik wrote:
> Hi again,
>
> This set contains fixes from 5.16 to 5.17. The normal testing was run
> for this set with no regressions found.
>
> Some refactoring patches were included in this set as dependencies:
>
> bf2307b19513 xfs: fold perag loop iteration logic into helper function
> dependency for f1788b5e5ee25bedf00bb4d25f82b93820d61189
> f1788b5e5ee2 xfs: rename the next_agno perag iteration variable
> dependency for 8ed004eb9d07a5d6114db3e97a166707c186262d
All now queued up, thanks.
greg k-h
prev parent reply other threads:[~2022-07-23 15:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-21 21:36 [PATCH 5.15 v2 0/6] xfs stable candidate patches for 5.15.y (part 3) Leah Rumancik
2022-07-21 21:36 ` [PATCH 5.15 v2 1/6] xfs: fix maxlevels comparisons in the btree staging code Leah Rumancik
2022-07-21 21:36 ` [PATCH 5.15 v2 2/6] xfs: fold perag loop iteration logic into helper function Leah Rumancik
2022-07-21 21:36 ` [PATCH 5.15 v2 3/6] xfs: rename the next_agno perag iteration variable Leah Rumancik
2022-07-21 21:36 ` [PATCH 5.15 v2 4/6] xfs: terminate perag iteration reliably on agcount Leah Rumancik
2022-07-21 21:36 ` [PATCH 5.15 v2 5/6] xfs: fix perag reference leak on iteration race with growfs Leah Rumancik
2022-07-21 21:36 ` [PATCH 5.15 v2 6/6] xfs: prevent a WARN_ONCE() in xfs_ioc_attr_list() Leah Rumancik
2022-07-23 15:25 ` 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=YtwS0l617OyO9Hop@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=amir73il@gmail.com \
--cc=leah.rumancik@gmail.com \
--cc=linux-xfs@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.