From: Christoph Hellwig <hch@lst.de>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: David Chinner <david@fromorbit.com>,
Carlos Maiolino <cem@kernel.org>, Christoph Hellwig <hch@lst.de>,
linux-xfs@vger.kernel.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: Fixes tag needs some work in the xfs tree
Date: Thu, 18 Dec 2025 06:09:26 +0100 [thread overview]
Message-ID: <20251218050926.GA1764@lst.de> (raw)
In-Reply-To: <20251218080618.2e214d02@canb.auug.org.au>
On Thu, Dec 18, 2025 at 08:06:18AM +1100, Stephen Rothwell wrote:
> Hi all,
>
> In commit
>
> 8dc15b7a6e59 ("xfs: fix XFS_ERRTAG_FORCE_ZERO_RANGE for zoned file system")
>
> Fixes tag
>
> Fixes: ea9989668081 ("xfs: error tag to force zeroing on debug kernels")
>
> has these problem(s):
>
> - Target SHA1 does not exist
>
> Maybe you meant
>
> Fixes: 66d78a11479c ("xfs: error tag to force zeroing on debug kernels")
Yes, that's correct.
next prev parent reply other threads:[~2025-12-18 5:09 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-17 21:06 linux-next: Fixes tag needs some work in the xfs tree Stephen Rothwell
2025-12-18 5:09 ` Christoph Hellwig [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-02-11 21:21 Stephen Rothwell
2025-02-11 22:31 ` Darrick J. Wong
2025-02-12 15:52 ` Carlos Maiolino
2024-10-08 20:06 Stephen Rothwell
2023-09-19 7:25 Stephen Rothwell
2023-06-05 4:22 Stephen Rothwell
2020-05-10 20:49 Stephen Rothwell
2020-04-16 22:19 Stephen Rothwell
2019-12-19 20:48 Stephen Rothwell
2019-08-12 21:45 Stephen Rothwell
2019-01-29 20:56 Stephen Rothwell
2019-01-29 22:08 ` Dave Chinner
2019-01-29 23:06 ` Stephen Rothwell
2019-01-29 23:43 ` Dave Chinner
2019-01-30 0:02 ` Stephen Rothwell
2019-01-30 0:38 ` Dave Chinner
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=20251218050926.GA1764@lst.de \
--to=hch@lst.de \
--cc=cem@kernel.org \
--cc=david@fromorbit.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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