From: Linus Torvalds <torvalds@linux-foundation.org>
To: Kent Overstreet <kent.overstreet@linux.dev>
Cc: linux-bcachefs@vger.kernel.org, linux-fsdevel@vger.kernel.org,
	 linux-kerenl@vger.kernel.org
Subject: Re: [GIT PULL] bcachefs fixes for 6.16-rc4
Date: Thu, 26 Jun 2025 20:21:23 -0700	[thread overview]
Message-ID: <CAHk-=wi+k8E4kWR8c-nREP0+EA4D+=rz5j0Hdk3N6cWgfE03-Q@mail.gmail.com> (raw)
In-Reply-To: <ahdf2izzsmggnhlqlojsnqaedlfbhomrxrtwd2accir365aqtt@6q52cm56jmuf>

On Thu, 26 Jun 2025 at 19:23, Kent Overstreet <kent.overstreet@linux.dev> wrote:
>
> per the maintainer thread discussion and precedent in xfs and btrfs
> for repair code in RCs, journal_rewind is again included

I have pulled this, but also as per that discussion, I think we'll be
parting ways in the 6.17 merge window.

You made it very clear that I can't even question any bug-fixes and I
should just pull anything and everything.

Honestly, at that point, I don't really feel comfortable being
involved at all, and the only thing we both seemed to really
fundamentally agree on in that discussion was "we're done".

              Linus

next prev parent reply	other threads:[~2025-06-27  3:21 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-27  2:22 [GIT PULL] bcachefs fixes for 6.16-rc4 Kent Overstreet
2025-06-27  3:21 ` Linus Torvalds [this message]
2025-06-27  3:34   ` Kent Overstreet
2025-07-01 14:43     ` John Stoffel
2025-07-02 16:34       ` Kent Overstreet
2025-07-02 17:41         ` Carl E. Thompson
2025-07-02 17:53           ` Kent Overstreet
2025-07-02 18:49             ` Malte Schröder
2025-07-07 20:03         ` John Stoffel
2025-07-07 20:39           ` Kent Overstreet
2025-07-07 21:35             ` Jani Partanen
2025-07-07 22:10               ` Kent Overstreet
2025-07-07 21:32           ` Carl E. Thompson
2025-07-07 22:22             ` Kent Overstreet
2025-07-04  7:02     ` Hillf Danton
2025-06-27 19:07   ` Kyle Sanderson
2025-06-27 19:16     ` Kyle Sanderson
2025-06-27 19:42       ` Kent Overstreet
2025-06-28  8:06   ` Gerhard Wiesinger
2025-06-27  3:33 ` pr-tracker-bot
2025-06-27 14:46 ` Josef Bacik
2025-06-28  1:59   ` Theodore Ts'o

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='CAHk-=wi+k8E4kWR8c-nREP0+EA4D+=rz5j0Hdk3N6cWgfE03-Q@mail.gmail.com' \
    --to=torvalds@linux-foundation.org \
    --cc=kent.overstreet@linux.dev \
    --cc=linux-bcachefs@vger.kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kerenl@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

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.