public inbox for linux-kernel@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: Fri, 11 Apr 2025 15:57:51 +1000	[thread overview]
Message-ID: <20250411155751.03bda841@canb.auug.org.au> (raw)

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

Hi all,

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

  7dbcd51dd047 ("bcachefs: Fix UAF in bchfs_read()")
  ff89dfe4d59e ("bcachefs: Use cpu_to_le16 for dirent lengths")
  6c14329d3da1 ("bcachefs: Fix type for parameter in journal_advance_devs_to_next_bucket")
  d589fb60c015 ("bcachefs: Fix escape sequence in prt_printf")

These are commits

  34b47e3d73a2 ("bcachefs: Fix UAF in bchfs_read()")
  4a22a7332341 ("bcachefs: Use cpu_to_le16 for dirent lengths")
  afc5444e4d86 ("bcachefs: Fix type for parameter in journal_advance_devs_to_next_bucket")
  f5cd27ec7146 ("bcachefs: Fix escape sequence in prt_printf")

in Linus' tree.

-- 
Cheers,
Stephen Rothwell

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

             reply	other threads:[~2025-04-11  5:57 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-11  5:57 Stephen Rothwell [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-11-10 21:11 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=20250411155751.03bda841@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=kent.overstreet@linux.dev \
    --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