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: Fri, 13 Jan 2023 10:27:07 +1100 [thread overview]
Message-ID: <20230113102707.649f0938@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 1607 bytes --]
Hi all,
The following commits are duplicated in the btrfs tre and also in the
btrfs-fixes tree as different commits (but the same patches):
6d3d970b2735 ("btrfs: fix missing error handling when logging directory items")
8bb6898da627 ("btrfs: fix directory logging due to race with concurrent index key deletion")
94cd63ae6799 ("btrfs: add missing setup of log for full commit at add_conflicting_inode()")
16199ad9eb6d ("btrfs: do not abort transaction on failure to write log tree when syncing log")
09e44868f1e0 ("btrfs: do not abort transaction on failure to update log root")
and
18c166730923 ("btrfs: fix missing error handling when logging directory items")
5c7eafa405c4 ("btrfs: fix directory logging due to race with concurrent index key deletion")
db260d6a0abb ("btrfs: add missing setup of log for full commit at add_conflicting_inode()")
ab6e0ba0377d ("btrfs: do not abort transaction on failure to write log tree when syncing log")
40c7d0525fcd ("btrfs: do not abort transaction on failure to update log root")
in the btrfs tree and
8ba46a395c7f ("btrfs: fix missing error handling when logging directory items")
46fc636870f4 ("btrfs: fix directory logging due to race with concurrent index key deletion")
52bd17801bcb ("btrfs: add missing setup of log for full commit at add_conflicting_inode()")
3d223cb5a2f7 ("btrfs: do not abort transaction on failure to write log tree when syncing log")
b8a4b882f62c ("btrfs: do not abort transaction on failure to update log root")
in the btrfs-fixes tree.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2023-01-12 23:27 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-12 23:27 Stephen Rothwell [this message]
2023-01-13 11:20 ` linux-next: duplicate patches in the btrfs tree David Sterba
-- strict thread matches above, loose matches on Subject: below --
2023-01-27 5:03 Stephen Rothwell
2023-02-10 0:19 Stephen Rothwell
2023-05-18 1:09 Stephen Rothwell
2023-07-19 0:28 Stephen Rothwell
2023-09-13 23:54 Stephen Rothwell
2023-09-14 23:32 Stephen Rothwell
2023-09-25 1:50 Stephen Rothwell
2023-11-15 22:31 Stephen Rothwell
2023-12-08 0:08 Stephen Rothwell
2024-01-17 0:45 Stephen Rothwell
2024-02-19 23:47 Stephen Rothwell
2024-04-03 23:04 Stephen Rothwell
2024-04-19 0:37 Stephen Rothwell
2024-04-26 0:18 Stephen Rothwell
2024-07-25 23:50 Stephen Rothwell
2024-08-15 22:53 Stephen Rothwell
2024-09-02 23:33 Stephen Rothwell
2024-09-04 22:20 ` Stephen Rothwell
2024-09-17 21:53 Stephen Rothwell
2024-09-23 22:04 Stephen Rothwell
2024-10-17 22:53 Stephen Rothwell
2024-10-31 22:25 Stephen Rothwell
2024-12-18 22:26 Stephen Rothwell
2025-01-20 22:46 Stephen Rothwell
2025-02-09 21:45 Stephen Rothwell
2025-04-22 22:29 Stephen Rothwell
2025-04-23 0:32 ` Stephen Rothwell
2025-05-12 22:50 Stephen Rothwell
2025-06-29 22:52 Stephen Rothwell
2025-07-01 23:59 Stephen Rothwell
2025-07-07 23:48 Stephen Rothwell
2025-07-15 23:24 Stephen Rothwell
2025-07-21 23:24 Stephen Rothwell
2025-11-24 22:39 Stephen Rothwell
2025-12-17 22:26 Stephen Rothwell
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=20230113102707.649f0938@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