From: Stephen Rothwell <sfr@canb•auug.org.au>
To: David Sterba <dsterba@suse•cz>
Cc: Linux Kernel Mailing List <linux-kernel@vger•kernel.org>,
Linux Next Mailing List <linux-next@vger•kernel.org>
Subject: linux-next: duplicate patches in the btrfs tree
Date: Mon, 30 Jun 2025 08:52:53 +1000 [thread overview]
Message-ID: <20250630085253.4e8389e6@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 1396 bytes --]
Hi all,
The following commits are also in the btrfs-fixes tree as different
commits (but the same patches):
6607ce31017f ("btrfs: use btrfs_record_snapshot_destroy() during rmdir")
255265e977c3 ("btrfs: propagate last_unlink_trans earlier when doing a rmdir")
2b6f3e452411 ("btrfs: record new subvolume in parent dir earlier to avoid dir logging races")
9fbec8743318 ("btrfs: fix inode lookup error handling during log replay")
6437c70ad4e5 ("btrfs: fix iteration of extrefs during log replay")
ae82071b0de6 ("btrfs: fix missing error handling when searching for inode refs during log replay")
731321790c83 ("btrfs: fix failure to rebuild free space tree using multiple transactions")
These are commits
157501b04699 ("btrfs: use btrfs_record_snapshot_destroy() during rmdir")
c466e33e729a ("btrfs: propagate last_unlink_trans earlier when doing a rmdir")
bf5bcf9a6fa0 ("btrfs: record new subvolume in parent dir earlier to avoid dir logging races")
5f61b961599a ("btrfs: fix inode lookup error handling during log replay")
54a7081ed168 ("btrfs: fix iteration of extrefs during log replay")
6561a40ceced ("btrfs: fix missing error handling when searching for inode refs during log replay")
1e6ed33cabba ("btrfs: fix failure to rebuild free space tree using multiple transactions")
in the btrfs-fixes tree.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2025-06-29 22:53 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-29 22:52 Stephen Rothwell [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-12-17 22:26 linux-next: duplicate patches in the btrfs tree Stephen Rothwell
2025-11-24 22:39 Stephen Rothwell
2025-07-21 23:24 Stephen Rothwell
2025-07-15 23:24 Stephen Rothwell
2025-07-07 23:48 Stephen Rothwell
2025-07-01 23:59 Stephen Rothwell
2025-05-12 22:50 Stephen Rothwell
2025-04-22 22:29 Stephen Rothwell
2025-04-23 0:32 ` Stephen Rothwell
2025-02-09 21:45 Stephen Rothwell
2025-01-20 22:46 Stephen Rothwell
2024-12-18 22:26 Stephen Rothwell
2024-10-31 22:25 Stephen Rothwell
2024-10-17 22:53 Stephen Rothwell
2024-09-23 22:04 Stephen Rothwell
2024-09-17 21:53 Stephen Rothwell
2024-09-02 23:33 Stephen Rothwell
2024-09-04 22:20 ` Stephen Rothwell
2024-08-15 22:53 Stephen Rothwell
2024-07-25 23:50 Stephen Rothwell
2024-04-26 0:18 Stephen Rothwell
2024-04-19 0:37 Stephen Rothwell
2024-04-03 23:04 Stephen Rothwell
2024-02-19 23:47 Stephen Rothwell
2024-01-17 0:45 Stephen Rothwell
2023-12-08 0:08 Stephen Rothwell
2023-11-15 22:31 Stephen Rothwell
2023-09-25 1:50 Stephen Rothwell
2023-09-14 23:32 Stephen Rothwell
2023-09-13 23:54 Stephen Rothwell
2023-07-19 0:28 Stephen Rothwell
2023-05-18 1:09 Stephen Rothwell
2023-02-10 0:19 Stephen Rothwell
2023-01-27 5:03 Stephen Rothwell
2023-01-12 23:27 Stephen Rothwell
2023-01-13 11:20 ` David Sterba
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=20250630085253.4e8389e6@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=dsterba@suse$(echo .)cz \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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