From: Stephen Rothwell <sfr@canb.auug.org.au>
To: "Darrick J. Wong" <djwong@kernel.org>,
David Chinner <david@fromorbit.com>, <linux-xfs@vger.kernel.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: linux-next: Fixes tag needs some work in the xfs tree
Date: Mon, 5 Jun 2023 14:22:30 +1000 [thread overview]
Message-ID: <20230605142230.2ee1f616@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 427 bytes --]
Hi all,
In commit
6a458bebafe7 ("xfs: fix broken logic when detecting mergeable bmap records")
Fixes tag
Fixes: 6bc6c99a944c ("xfs: alert the user about data/attr fork mappings that could be merged")
has these problem(s):
- Target SHA1 does not exist
Maybe you meant
Fixes: 336642f79283 ("xfs: alert the user about data/attr fork mappings that could be merged")
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2023-06-05 4:22 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-05 4:22 Stephen Rothwell [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-12-17 21:06 linux-next: Fixes tag needs some work in the xfs tree Stephen Rothwell
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
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=20230605142230.2ee1f616@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=david@fromorbit.com \
--cc=djwong@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux-xfs@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;
as well as URLs for NNTP newsgroup(s).