From: Sam James <sam@gentoo.org>
To: leah.rumancik@gmail.com
Cc: stable@vger.kernel.org, Miaohe Lin <linmiaohe@huawei.com>
Subject: Re: [PATCH 6.6] backport: fix 6.6 backport of changes to fork
Date: Fri, 14 Jun 2024 05:55:46 +0100 [thread overview]
Message-ID: <87zfro3yy5.fsf@gentoo.org> (raw)
In-Reply-To: <CACzhbgRjDNkpaQOYsUN+v+jn3E2DVxX0Q4WuQWNjfwEx4Fps6g@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 92 bytes --]
Is it worth reverting the original bad backport for now, given it causes
xfstests failures?
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 377 bytes --]
next prev parent reply other threads:[~2024-06-14 4:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-03 23:25 [PATCH 6.6] backport: fix 6.6 backport of changes to fork Leah Rumancik
2024-06-12 0:31 ` Leah Rumancik
2024-06-14 4:55 ` Sam James [this message]
2024-06-14 6:41 ` Greg KH
2024-06-14 8:52 ` Sam James
2024-06-14 9:08 ` Greg KH
2024-06-14 17:45 ` 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=87zfro3yy5.fsf@gentoo.org \
--to=sam@gentoo.org \
--cc=leah.rumancik@gmail.com \
--cc=linmiaohe@huawei.com \
--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