public inbox for stable@vger.kernel.org
 help / color / mirror / Atom feed
From: Tim Chen <tim.c.chen@linux.intel.com>
To: K Prateek Nayak <kprateek.nayak@amd.com>,
	Greg KH <gregkh@linuxfoundation.org>
Cc: stable@vger.kernel.org, Peter Zijlstra <peterz@infradead.org>,
	Ingo Molnar	 <mingo@kernel.org>,
	Juri Lelli <juri.lelli@redhat.com>,
	Dietmar Eggemann	 <dietmar.eggemann@arm.com>,
	Ben Segall <bsegall@google.com>, Mel Gorman	 <mgorman@suse.de>,
	Valentin Schneider <vschneid@redhat.com>,
	Tim Chen	 <tim.c.chen@intel.com>,
	Vincent Guittot <vincent.guittot@linaro.org>,
	Len Brown	 <len.brown@intel.com>,
	linux-kernel@vger.kernel.org, Chen Yu <yu.c.chen@intel.com>,
	 "Gautham R . Shenoy" <gautham.shenoy@amd.com>,
	Zhao Liu <zhao1.liu@intel.com>,
	Vinicius Costa Gomes <vinicius.gomes@intel.com>,
	Arjan Van De Ven <arjan.van.de.ven@intel.com>
Subject: Re: [PATCH 6.18 2/2] sched/topology: Fix sched domain build error for GNR, CWF in SNC-3 mode
Date: Mon, 09 Feb 2026 11:21:12 -0800	[thread overview]
Message-ID: <b5e9109e4be90f596da9c12cbb2e6bf0bf55a0c6.camel@linux.intel.com> (raw)
In-Reply-To: <f391338d-49bd-4383-a8cd-0dd8073da764@amd.com>

On Mon, 2026-02-09 at 09:29 +0530, K Prateek Nayak wrote:
> Hello Greg,
> 
> On 2/7/2026 8:59 PM, Greg KH wrote:
> > This breaks the build:
> >   CC      arch/x86/kernel/smpboot.o
> > arch/x86/kernel/smpboot.c:548:5: error: no previous prototype for ‘arch_sched_node_distance’ [-Werror=missing-prototypes]
> >   548 | int arch_sched_node_distance(int from, int to)
> >       |     ^~~~~~~~~~~~~~~~~~~~~~~~
> > cc1: all warnings being treated as errors
> > 
> > How was it tested?
> 
> I believe this build issue was fixed by upstream commit 73cbcfe255f7
> ("sched/topology,x86: Fix build warning")
> 
> (Full upstream SHA: 73cbcfe255f7edca915d978a7d1b0a11f2d62812)
> 
> P.S. It cherry-picks cleanly on top of "Linux 6.18.9".

Pratek,

Thanks for pointing to the patch.

Tim

      reply	other threads:[~2026-02-09 19:21 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-05 21:33 [PATCH 6.18 0/2] Fix NUMA sched domain build errors for GNR and CWF Tim Chen
2026-02-05 21:33 ` [PATCH 6.18 1/2] sched: Create architecture specific sched domain distances Tim Chen
2026-02-05 21:33 ` [PATCH 6.18 2/2] sched/topology: Fix sched domain build error for GNR, CWF in SNC-3 mode Tim Chen
2026-02-07 15:29   ` Greg KH
2026-02-09  3:59     ` K Prateek Nayak
2026-02-09 19:21       ` Tim Chen [this message]

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=b5e9109e4be90f596da9c12cbb2e6bf0bf55a0c6.camel@linux.intel.com \
    --to=tim.c.chen@linux.intel.com \
    --cc=arjan.van.de.ven@intel.com \
    --cc=bsegall@google.com \
    --cc=dietmar.eggemann@arm.com \
    --cc=gautham.shenoy@amd.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=juri.lelli@redhat.com \
    --cc=kprateek.nayak@amd.com \
    --cc=len.brown@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mgorman@suse.de \
    --cc=mingo@kernel.org \
    --cc=peterz@infradead.org \
    --cc=stable@vger.kernel.org \
    --cc=tim.c.chen@intel.com \
    --cc=vincent.guittot@linaro.org \
    --cc=vinicius.gomes@intel.com \
    --cc=vschneid@redhat.com \
    --cc=yu.c.chen@intel.com \
    --cc=zhao1.liu@intel.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