mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: Pnina Feder <pnina.feder@mobileye.com>
Cc: pmladek@suse.com, bhe@redhat.com, linux-kernel@vger.kernel.org,
	lkp@intel.com, mgorman@suse.de, mingo@redhat.com,
	peterz@infradead.org, rostedt@goodmis.org,
	senozhatsky@chromium.org, tglx@linutronix.de,
	vkondra@mobileye.com
Subject: Re: [PATCH v1] panic: add panic_redirect_cpu declaration to header
Date: Sun, 18 Jan 2026 12:44:34 -0800	[thread overview]
Message-ID: <20260118124434.1373ffe0f314019381257a7f@linux-foundation.org> (raw)
In-Reply-To: <20260118120149.986849-1-pnina.feder@mobileye.com>

On Sun, 18 Jan 2026 14:01:49 +0200 Pnina Feder <pnina.feder@mobileye.com> wrote:

> Add the extern declaration for panic_redirect_cpu to linux/panic.h
> to fix the sparse warning:
> 
>   kernel/panic.c:305:10: sparse: sparse: symbol 'panic_redirect_cpu'
>   was not declared. Should it be static?
> 
> The variable needs to be declared in the header alongside panic_cpu
> since it is used for synchronization when redirecting panic to a
> specific CPU via the panic_force_cpu= boot parameter.
> 

Thanks, I added this as a squashable fix against your earlier patch
"panic: add panic_force_cpu= parameter to redirect panic to a specific
CPU".

(It's nice to tell people when a patch fixes a pending patch in this
manner - otherwise everyone has to run around trying to figure out
which tree is being patched and why).

      reply	other threads:[~2026-01-18 20:44 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-18 12:01 Pnina Feder
2026-01-18 20:44 ` Andrew Morton [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=20260118124434.1373ffe0f314019381257a7f@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=bhe@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkp@intel.com \
    --cc=mgorman@suse.de \
    --cc=mingo@redhat.com \
    --cc=peterz@infradead.org \
    --cc=pmladek@suse.com \
    --cc=pnina.feder@mobileye.com \
    --cc=rostedt@goodmis.org \
    --cc=senozhatsky@chromium.org \
    --cc=tglx@linutronix.de \
    --cc=vkondra@mobileye.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®