[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAHk-=wj-t1N7a2dH=y7MCjctk_Zw77C8_V6cfS-UC7f3jXAF6g@mail.gmail.com>
Date: Fri, 28 Apr 2023 15:02:54 -0700
From: Linus Torvalds <torvalds@...ux-foundation.org>
To: Ingo Molnar <mingo@...nel.org>,
Mathieu Desnoyers <mathieu.desnoyers@...icios.com>,
Andrew Morton <akpm@...ux-foundation.org>
Cc: linux-kernel@...r.kernel.org,
Peter Zijlstra <peterz@...radead.org>,
Thomas Gleixner <tglx@...utronix.de>,
Borislav Petkov <bp@...en8.de>,
Juri Lelli <juri.lelli@...hat.com>,
Vincent Guittot <vincent.guittot@...aro.org>,
Dietmar Eggemann <dietmar.eggemann@....com>,
Steven Rostedt <rostedt@...dmis.org>,
Ben Segall <bsegall@...gle.com>, Mel Gorman <mgorman@...e.de>,
Daniel Bristot de Oliveira <bristot@...hat.com>,
Valentin Schneider <vschneid@...hat.com>
Subject: Re: [GIT PULL] scheduler changes for v6.4
On Thu, Apr 27, 2023 at 1:51 PM Ingo Molnar <mingo@...nel.org> wrote:
>
> - Fix performance regression introduced by mm_cid
This causes a conflict with commit b20b0368c614 ("mm: fix memory leak
on mm_init error handling") that came in through the MM tree.
That conflict is trivial to resolve, and I did so.
Except I also checked my resolution with what was going on in
linux-next, and it's different.
I'm pretty sure the resolution in linux-next is wrong, but I thought
I'd mention this, since clearly this wasn't caught in linux-next.
Or maybe it's me that did it wrong, but hey, that couldn't actually
happen, could it?
Linus
Powered by blists - more mailing lists