Subject: linux-next: duplicate patches in the btrfs tree

From: Stephen Rothwell <[email-masked]>
Date: Mon, 30 Jun 2025 08:52:53 +1000

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