[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <YjL+9sUPLvE57GE0@zn.tnic>
Date: Thu, 17 Mar 2022 10:27:18 +0100
From: Borislav Petkov <bp@...en8.de>
To: Ammar Faizi <ammarfaizi2@...weeb.org>
Cc: Thomas Gleixner <tglx@...utronix.de>,
Alviro Iskandar Setiawan <alviro.iskandar@...il.com>,
Alviro Iskandar Setiawan <alviro.iskandar@...weeb.org>,
David.Laight@...lab.com, Dave Hansen <dave.hansen@...ux.intel.com>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
"H. Peter Anvin" <hpa@...or.com>, Ingo Molnar <mingo@...hat.com>,
Tony Luck <tony.luck@...el.com>,
Yazen Ghannam <yazen.ghannam@....com>,
linux-edac@...r.kernel.org, linux-kernel@...r.kernel.org,
stable@...r.kernel.org,
GNU/Weeb Mailing List <gwml@...r.gnuweeb.org>, x86@...nel.org
Subject: Re: [PATCH v5 0/2] Two x86 fixes
On Thu, Mar 17, 2022 at 03:19:07PM +0700, Ammar Faizi wrote:
> On Thu, Mar 10, 2022 at 8:53 AM Ammar Faizi wrote:
> > Two x86 fixes in this series.
> >
> > 1) x86/delay: Fix the wrong Assembly constraint in delay_loop() function.
> > 2) x86/MCE/AMD: Fix memory leak when `threshold_create_bank()` fails.
>
> Ping (1)!
> Borislav? Thomas?
Yes, what's up?
Are those urgent fixes which break some use case or can you simply sit
patiently and wait?
Because we have an upcoming merge window and we need to prepare for
that. And there are real bugs that need fixing too.
So what's the rush here?
--
Regards/Gruss,
Boris.
https://people.kernel.org/tglx/notes-about-netiquette
Powered by blists - more mailing lists