linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Kent Overstreet <kent.overstreet@linux.dev>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	linux-mm@kvack.org,  linux-kernel@vger.kernel.org,
	mm-commits@vger.kernel.org
Subject: Re: [GIT PULL] non-MM updates for 6.11-rc1
Date: Sun, 21 Jul 2024 23:35:38 -0400	[thread overview]
Message-ID: <yebpkzq53mcpzf3366jxksf7w6npa5bpsiqinom74ivzutofke@m7os33wmq3fx> (raw)
In-Reply-To: <CAHk-=whqXizOqcpcrqvRJ88Twi4+o=G1Y=5qsLBs5R-8uHjs+Q@mail.gmail.com>

On Sun, Jul 21, 2024 at 06:12:37PM GMT, Linus Torvalds wrote:
> On Sun, 21 Jul 2024 at 15:10, Andrew Morton <akpm@linux-foundation.org> wrote:
> >
> > - In the series "treewide: Refactor heap related implementation",
> >   Kuan-Wei Chiu has significantly reworked the min_heap library code and
> >   has taught bcachefs to use the new more generic implementation.
> 
> Bah. I think the users should probably have been converted in their
> own trees, instead of having this thing that caused a somewhat nasty
> conflict.
> 
> I think I sorted it out correctly, but I'm not seeing why the bcachefs
> conversion was done outside the bcachefs tree.

Ergh, this turned out awkward. I originally planning on sending you that
series, but Andrew picked it up - and splitting the bcachefs patches out
from the rest of the series would made it awkward to keep track of, but
perhaps that was justified here.

I think this must have been missed in -next as well because the clock.c
changes came late (there was a bug that was uncovered by some out of
tree code, and I'm still sitting on that patch but the bug was worth
fixing).

> Kent, mind checking that I didn't do something horribly horribly bad?

Looks good, and nothing's immediately exploding when I test it, kasan
included, so I think we're good.


  reply	other threads:[~2024-07-22  3:35 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-21 22:10 Andrew Morton
2024-07-22  1:12 ` Linus Torvalds
2024-07-22  3:35   ` Kent Overstreet [this message]
2024-07-22  1:15 ` pr-tracker-bot

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=yebpkzq53mcpzf3366jxksf7w6npa5bpsiqinom74ivzutofke@m7os33wmq3fx \
    --to=kent.overstreet@linux.dev \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mm-commits@vger.kernel.org \
    --cc=torvalds@linux-foundation.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