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 patch in the btrfs tree
Date: Fri, 8 Nov 2024 09:03:17 +1100 [thread overview]
Message-ID: <20241108090317.3eaad84e@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 332 bytes --]
Hi all,
The following commit is also in the btrfs-fixes tree as a different commit
(but the same patch):
f4c30cb4a62e ("btrfs: fix the length of reserved qgroup to free")
This is commit
2b084d820594 ("btrfs: fix the length of reserved qgroup to free")
in the btrfs-fixes tree.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2024-11-07 22:03 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-07 22:03 Stephen Rothwell [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-01-14 22:40 linux-next: duplicate patch in the btrfs tree Stephen Rothwell
2024-12-08 22:45 Stephen Rothwell
2024-07-21 22:24 Stephen Rothwell
2024-05-15 7:03 Stephen Rothwell
2024-05-01 1:25 Stephen Rothwell
2024-03-25 22:36 Stephen Rothwell
2023-10-11 22:21 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=20241108090317.3eaad84e@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