[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <7288e28d6ada409b1b7dd6e9abea77b596bacf3c.camel@surriel.com>
Date: Wed, 12 Feb 2025 10:39:30 -0500
From: Rik van Riel <riel@...riel.com>
To: Peter Zijlstra <peterz@...radead.org>, Brendan Jackman
<jackmanb@...gle.com>
Cc: x86@...nel.org, linux-kernel@...r.kernel.org, bp@...en8.de,
dave.hansen@...ux.intel.com, zhengqi.arch@...edance.com,
nadav.amit@...il.com, thomas.lendacky@....com, kernel-team@...a.com,
linux-mm@...ck.org, akpm@...ux-foundation.org, jannh@...gle.com,
mhklinux@...look.com, andrew.cooper3@...rix.com
Subject: Re: [PATCH v10 00/12] AMD broadcast TLB invalidation
On Wed, 2025-02-12 at 11:59 +0100, Peter Zijlstra wrote:
> On Wed, Feb 12, 2025 at 11:44:01AM +0100, Brendan Jackman wrote:
> > They apply to 60675d4ca1ef0 ("Merge branch 'linus' into x86/mm, to
> > pick up fixes").
>
> Why some random commit? Shouldn't this be against a sensible branch
> or
> something, like perhaps tip/x86/mm ?
>
Let me rebase these against current tip/x86/mm
and apply the latest suggested cleanups!
--
All Rights Reversed.
Powered by blists - more mailing lists