linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
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, 26 Apr 2024 10:18:38 +1000	[thread overview]
Message-ID: <20240426101838.0cd78625@canb.auug.org.au> (raw)

[-- Attachment #1: Type: text/plain, Size: 309 bytes --]

Hi all,

The following commits are also in the bbtrfs-fixes tree as different
commits (but the same patches):

  7f1f55f2cdcd ("btrfs: add missing mutex_unlock in btrfs_relocate_sys_chunks()")
  8aa467899340 ("btrfs: take the cleaner_mutex earlier in qgroup disable")

-- 
Cheers,
Stephen Rothwell

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

             reply	other threads:[~2024-04-26  0:18 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-26  0:18 Stephen Rothwell [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-04-19  0:37 linux-next: duplicate patches in the btrfs tree 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=20240426101838.0cd78625@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=dsterba@suse.cz \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@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).