public inbox for linux-next@vger.kernel.org 
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Kent Overstreet <kent.overstreet@linux•dev>
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 bcachefs tree
Date: Mon, 11 Nov 2024 08:11:43 +1100	[thread overview]
Message-ID: <20241111081143.43a59204@canb.auug.org.au> (raw)

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

Hi all,

The following commits are also in Linus Torvalds' tree as different
commits (but the same patches):

  aaf086c1ee35 ("bcachefs: btree_cache.freeable list fixes")
  55fcef1f90d8 ("bcachefs: check the invalid parameter for perf test")
  52dc307cb782 ("bcachefs: add check NULL return of bio_kmalloc in journal_read_bucket")
  83c67792c91b ("bcachefs: Ensure BCH_FS_may_go_rw is set before exiting recovery")
  85a62009bd05 ("bcachefs: Fix topology errors on split after merge")
  88f16c7b82a8 ("bcachefs: Ancient versions with bad bkey_formats are no longer supported")
  9d3e24c46b19 ("bcachefs: Fix error handling in bch2_btree_node_prefetch()")
  dccaf5e5a6cd ("bcachefs: Fix null ptr deref in bucket_gen_get()")

These are commits

  baefd3f849ed ("bcachefs: btree_cache.freeable list fixes")
  9bb33852f5cc ("bcachefs: check the invalid parameter for perf test")
  93d53f1caf2c ("bcachefs: add check NULL return of bio_kmalloc in journal_read_bucket")
  ef4f6c322bf4 ("bcachefs: Ensure BCH_FS_may_go_rw is set before exiting recovery")
  cec136d348e0 ("bcachefs: Fix topology errors on split after merge")
  d335bb3fd3a4 ("bcachefs: Ancient versions with bad bkey_formats are no longer supported")
  72acab3a7c5a ("bcachefs: Fix error handling in bch2_btree_node_prefetch()")
  fd00045f383f ("bcachefs: Fix null ptr deref in bucket_gen_get()")

in Linus' tree.

-- 
Cheers,
Stephen Rothwell

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

             reply	other threads:[~2024-11-10 21:11 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-10 21:11 Stephen Rothwell [this message]
  -- strict thread matches above, loose matches on Subject: below --
2025-04-11  5:57 linux-next: duplicate patches in the bcachefs tree Stephen Rothwell
2024-11-03 22:01 Stephen Rothwell
2024-10-24 20:44 Stephen Rothwell
2024-07-14 21:33 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=20241111081143.43a59204@canb.auug.org.au \
    --to=sfr@canb$(echo .)auug.org.au \
    --cc=kent.overstreet@linux$(echo .)dev \
    --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