From: "Arnd Bergmann" <arnd@arndb.de>
To: "Borislav Petkov" <bp@alien8.de>, "Arnd Bergmann" <arnd@kernel.org>
Cc: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>,
"Thomas Gleixner" <tglx@linutronix.de>,
"Ingo Molnar" <mingo@redhat.com>,
"Dave Hansen" <dave.hansen@linux.intel.com>,
x86@kernel.org, "H. Peter Anvin" <hpa@zytor.com>,
"Mario Limonciello" <mario.limonciello@amd.com>,
"Bjorn Helgaas" <bhelgaas@google.com>,
"Yazen Ghannam" <yazen.ghannam@amd.com>,
"Suma Hegde" <suma.hegde@amd.com>,
"Naveen Krishna Chatradhi" <naveenkrishna.chatradhi@amd.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] platform/x86/amd/hsmp: fix compile-testing without CONFiG_AMD_NB
Date: Tue, 29 Oct 2024 10:56:12 +0000 [thread overview]
Message-ID: <3a5360a4-e5c7-4c97-ab15-778d73f5b5a6@app.fastmail.com> (raw)
In-Reply-To: <20241029103316.GBZyC57KGSxyPie3Qu@fat_crate.local>
On Tue, Oct 29, 2024, at 10:33, Borislav Petkov wrote:
> On Tue, Oct 29, 2024 at 09:23:20AM +0000, Arnd Bergmann wrote:
>>
>> #define amd_nb_num(x) 0
>> #define amd_nb_has_feature(x) false
>> -#define node_to_amd_nb(x) NULL
>> +static inline struct amd_northbridge *node_to_amd_nb(int node)
>> +{
>> + return NULL;
>> +}
>> #define amd_gart_present(x) false
>
> ... so this fix should go to Linus now so that build testing doesn't break?
>
That would work, or Ilpo can pick it into the tree that
has the driver changes, possibly folding the fix into the
other changes.
Arnd
next prev parent reply other threads:[~2024-10-29 10:56 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-29 9:23 Arnd Bergmann
2024-10-29 10:33 ` Borislav Petkov
2024-10-29 10:56 ` Arnd Bergmann [this message]
2024-10-29 11:06 ` Borislav Petkov
2024-10-29 12:40 ` Ilpo Järvinen
2024-10-29 14:11 ` Borislav Petkov
2024-10-29 15:04 ` Ilpo Järvinen
2024-10-29 12:39 ` Ilpo Järvinen
2024-10-29 15:11 ` Borislav Petkov
2024-10-29 15:19 ` Ilpo Järvinen
2024-10-29 15:59 ` Borislav Petkov
2024-10-29 17:35 ` [tip: x86/urgent] x86/amd_nb: Fix compile-testing without CONFIG_AMD_NB tip-bot2 for Arnd Bergmann
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3a5360a4-e5c7-4c97-ab15-778d73f5b5a6@app.fastmail.com \
--to=arnd@arndb.de \
--cc=arnd@kernel.org \
--cc=bhelgaas@google.com \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mario.limonciello@amd.com \
--cc=mingo@redhat.com \
--cc=naveenkrishna.chatradhi@amd.com \
--cc=suma.hegde@amd.com \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
--cc=yazen.ghannam@amd.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®