[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <SJ1PR11MB60835D7F85097FEF454DD74CFC879@SJ1PR11MB6083.namprd11.prod.outlook.com>
Date: Thu, 23 Mar 2023 18:10:31 +0000
From: "Luck, Tony" <tony.luck@...el.com>
To: Yazen Ghannam <yazen.ghannam@....com>
CC: Borislav Petkov <bp@...en8.de>,
"Smita.KoralahalliChannabasappa@....com"
<Smita.KoralahalliChannabasappa@....com>,
"dave.hansen@...ux.intel.com" <dave.hansen@...ux.intel.com>,
"hpa@...or.com" <hpa@...or.com>,
"linux-edac@...r.kernel.org" <linux-edac@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"x86@...nel.org" <x86@...nel.org>,
"patches@...ts.linux.dev" <patches@...ts.linux.dev>
Subject: RE: [PATCH v3 4/5] x86/mce: Move storm handling to core.
> Can this patch and the previous two be squashed together?
>
> Like so?
> Patch 1: Remove old code.
> Patch 2: Add new common and Intel-specific code.
> Patch 3: Add AMD-specific code.
Yazen,
Those three patches could be merged ... but they already seem big:
0002: 3 files changed, 158 insertions(+), 11 deletions(-)
0003: 3 files changed, 22 insertions(+), 2 deletions(-)
0004: 3 files changed, 100 insertions(+), 92 deletions(-)
Lumping them together wouldn't be the sum of those but would be worse (IMHO)
-Tony
Powered by blists - more mailing lists