From: Greg KH <gregkh@linuxfoundation.org>
To: Amir Goldstein <amir73il@gmail.com>
Cc: Mahmoud Adam <mngyadam@amazon.com>,
stable@vger.kernel.org, Theodore Ts'o <tytso@mit.edu>,
"Darrick J. Wong" <djwong@kernel.org>,
Leah Rumancik <lrumancik@google.com>
Subject: Re: [PATCH 6.1 0/6] backport xfs fix patches reported by xfs/179/270/557/606
Date: Thu, 11 Apr 2024 09:22:04 +0200 [thread overview]
Message-ID: <2024041144-curly-unscrew-bbb0@gregkh> (raw)
In-Reply-To: <CAOQ4uxg32LW0mmH=j9f6yoFOPOAVDaeJ2bLqz=yQ-LJOxWRiBg@mail.gmail.com>
On Fri, Apr 05, 2024 at 12:55:41PM +0300, Amir Goldstein wrote:
> On Fri, Apr 5, 2024 at 12:27 PM Greg KH <gregkh@linuxfoundation.org> wrote:
> >
> > On Thu, Apr 04, 2024 at 11:15:25AM +0200, Mahmoud Adam wrote:
> > > Amir Goldstein <amir73il@gmail.com> writes:
> > >
> > > > On Wed, Apr 3, 2024 at 9:18 PM Darrick J. Wong <djwong@kernel.org> wrote:
> > > >> To the group: Who's the appropriate person to handle these?
> > > >>
> > > >> Mahmoud: If the answer to the above is "???" or silence, would you be
> > > >> willing to take on stable testing and maintenance?
> > >
> > > Probably there is an answer now :). But Yes, I'm okay with doing that,
> > > Xfstests is already part for our nightly 6.1 testing.
>
> Let's wait for Leah to chime in and then decide.
> Leah's test coverage is larger than the tests that Mahmoud ran.
Ok, I'll drop these from my review queue now, when they are "good
enough" can someone resend them please?
thanks,
greg k-h
next prev parent reply other threads:[~2024-04-11 7:22 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-03 12:59 [PATCH 6.1 0/6] backport xfs fix patches reported by xfs/179/270/557/606 Mahmoud Adam
2024-04-03 12:59 ` [PATCH 6.1 1/6] xfs: allow inode inactivation during a ro mount log recovery Mahmoud Adam
2024-04-03 12:59 ` [PATCH 6.1 2/6] xfs: fix log recovery when unknown rocompat bits are set Mahmoud Adam
2024-04-03 12:59 ` [PATCH 6.1 3/6] xfs: get root inode correctly at bulkstat Mahmoud Adam
2024-04-03 12:59 ` [PATCH 6.1 4/6] xfs: short circuit xfs_growfs_data_private() if delta is zero Mahmoud Adam
2024-04-03 12:59 ` [PATCH 6.1 5/6] xfs: hoist refcount record merge predicates Mahmoud Adam
2024-04-03 12:59 ` [PATCH 6.1 6/6] xfs: estimate post-merge refcounts correctly Mahmoud Adam
2024-04-03 18:18 ` [PATCH 6.1 0/6] backport xfs fix patches reported by xfs/179/270/557/606 Darrick J. Wong
2024-04-04 5:45 ` Amir Goldstein
2024-04-04 9:15 ` Mahmoud Adam
2024-04-05 9:27 ` Greg KH
2024-04-05 9:55 ` Amir Goldstein
2024-04-11 7:22 ` Greg KH [this message]
2024-04-11 17:27 ` Leah Rumancik
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=2024041144-curly-unscrew-bbb0@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=amir73il@gmail.com \
--cc=djwong@kernel.org \
--cc=lrumancik@google.com \
--cc=mngyadam@amazon.com \
--cc=stable@vger.kernel.org \
--cc=tytso@mit.edu \
/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