[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <df0cb5c7-71ef-03ab-b0f5-7c95a4065ed4@linux.intel.com>
Date: Tue, 29 Oct 2024 14:40:00 +0200 (EET)
From: Ilpo Järvinen <ilpo.jarvinen@...ux.intel.com>
To: Borislav Petkov <bp@...en8.de>
cc: Arnd Bergmann <arnd@...db.de>, Arnd Bergmann <arnd@...nel.org>,
Thomas Gleixner <tglx@...utronix.de>, Ingo Molnar <mingo@...hat.com>,
Dave Hansen <dave.hansen@...ux.intel.com>, x86@...nel.org,
"H. Peter Anvin" <hpa@...or.com>,
Mario Limonciello <mario.limonciello@....com>,
Bjorn Helgaas <bhelgaas@...gle.com>, Yazen Ghannam <yazen.ghannam@....com>,
Suma Hegde <suma.hegde@....com>,
Naveen Krishna Chatradhi <naveenkrishna.chatradhi@....com>,
LKML <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] platform/x86/amd/hsmp: fix compile-testing without
CONFiG_AMD_NB
On Tue, 29 Oct 2024, Borislav Petkov wrote:
> On Tue, Oct 29, 2024 at 10:56:12AM +0000, Arnd Bergmann wrote:
> > That would work, or Ilpo can pick it into the tree that
> > has the driver changes, possibly folding the fix into the
> > other changes.
>
> Right, while it shouldn't be a problem, I'd like to keep all amd_nb changes in
> one tree because we have stuff in-flight touching and changing exactly that
> area so...
Hi Boris,
I'm unfortunately left a bit unsure what exactly is your suggestion here,
so could you please elaborate?
(I'm assuming the big amd_nb series will go through the x86 tree.)
Thanks in advance.
--
i.
Powered by blists - more mailing lists