[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <e02bd937-a11d-4deb-8d8c-f7304bcce39b@intel.com>
Date: Wed, 11 Feb 2026 10:01:25 -0800
From: Dave Hansen <dave.hansen@...el.com>
To: Xie Yuanbin <qq570070308@...il.com>, peterz@...radead.org,
tglx@...nel.org, riel@...riel.com, segher@...nel.crashing.org,
david@...nel.org, hpa@...or.com, arnd@...db.de, anna-maria@...utronix.de,
mingo@...hat.com, juri.lelli@...hat.com, vincent.guittot@...aro.org,
dietmar.eggemann@....com, rostedt@...dmis.org, bsegall@...gle.com,
mgorman@...e.de, vschneid@...hat.com, bp@...en8.de,
dave.hansen@...ux.intel.com, luto@...nel.org, houwenlong.hwl@...group.com,
frederic@...nel.org, akpm@...ux-foundation.org, lorenzo.stoakes@...cle.com,
bhe@...hat.com, ryan.roberts@....com, urezki@...il.com, nysal@...ux.ibm.com,
max.kellermann@...os.com
Cc: linux-kernel@...r.kernel.org, x86@...nel.org
Subject: Re: [PATCH v6 RESEND 1/3] x86/mm/tlb: Make enter_lazy_tlb() always
inline on x86
On 2/11/26 07:36, Xie Yuanbin wrote:
> However, I'm a little worried that moving
> '#define enter_lazy_tlb enter_lazy_tlb' into '#ifndef MODULE' might cause
> other issues, so I placed it outside '#ifndef MODULE' outside in my
> first patch.
What kind of issues?
I mean, if it compiles, it compiles, right? The robots are there to find
the crazy stuff for us.
Powered by blists - more mailing lists