[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <SN6PR12MB263902F373B6184FEB563B89F8EE0@SN6PR12MB2639.namprd12.prod.outlook.com>
Date: Fri, 14 Jun 2019 14:14:39 +0000
From: "Ghannam, Yazen" <Yazen.Ghannam@....com>
To: Borislav Petkov <bp@...en8.de>
CC: "linux-edac@...r.kernel.org" <linux-edac@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: RE: [PATCH 2/8] EDAC/amd64: Support more than two controllers for
chip selects handling
> -----Original Message-----
> From: linux-kernel-owner@...r.kernel.org <linux-kernel-owner@...r.kernel.org> On Behalf Of Borislav Petkov
> Sent: Thursday, June 13, 2019 5:23 PM
> To: Ghannam, Yazen <Yazen.Ghannam@....com>
> Cc: linux-edac@...r.kernel.org; linux-kernel@...r.kernel.org
> Subject: Re: [PATCH 2/8] EDAC/amd64: Support more than two controllers for chip selects handling
>
> On Thu, Jun 13, 2019 at 08:58:16PM +0000, Ghannam, Yazen wrote:
> > The first patch is meant as a fix for existing systems, and this patch
> > is to add new functionality.
> >
> > I can merge them together if you think that's more appropriate.
>
> Is it fixing such a critical issue that it needs to be a separate patch?
> If so, it should be CC:stable.
>
> But I think we've survived without it just fine so why bother. But maybe
> there's an aspect I'm missing...
>
No, you're right. It's not something critical.
I can squash these two patches together if you'd like.
Thanks,
Yazen
Powered by blists - more mailing lists