From: Andrew Morton <akpm@linux-foundation.org>
To: Mete Durlu <meted@linux.ibm.com>
Cc: Petr Mladek <pmladek@suse.com>,
Heiko Carstens <hca@linux.ibm.com>,
Vasily Gorbik <gor@linux.ibm.com>,
Alexander Gordeev <agordeev@linux.ibm.com>,
Christian Borntraeger <borntraeger@linux.ibm.com>,
Sven Schnelle <svens@linux.ibm.com>,
"David S. Miller" <davem@davemloft.net>,
Andreas Larsson <andreas@gaisler.com>,
Bradley Morgan <include@grrlz.net>,
linux-kernel@vger.kernel.org, linux-s390@vger.kernel.org,
sparclinux@vger.kernel.org
Subject: Re: [PATCH v6 0/3] Introduce arch_do_panic
Date: Mon, 31 Aug 2026 17:19:06 -0700 [thread overview]
Message-ID: <20260831171906.7520833ab8ac40d0369b0228@linux-foundation.org> (raw)
In-Reply-To: <20260831-arch_do_panic-v6-0-a1e170a9e7fd@linux.ibm.com>
On Mon, 31 Aug 2026 11:57:14 +0200 Mete Durlu <meted@linux.ibm.com> wrote:
> Replace architecture-specific ifdef sections in vpanic() with a clean
> arch_do_panic() hook. Currently s390 and sparc embed their panic
> handlers directly in vpanic() using preprocessor conditionals, making
> the common code path harder to maintain.
Nice little cleanup, thanks.
> arch/s390/kernel/traps.c | 7 +++++++
> arch/sparc/kernel/setup.c | 9 +++++++++
> include/linux/panic.h | 2 ++
> kernel/panic.c | 15 +++------------
> 4 files changed, 21 insertions(+), 12 deletions(-)
Why do cleanups make the kernel bigger. It's often that way.
I'll scoop it up. An ack from sparc people would be nice, please.
prev parent reply other threads:[~2026-09-01 0:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-31 9:57 Mete Durlu
2026-08-31 9:57 ` [PATCH v6 1/3] panic: " Mete Durlu
2026-08-31 9:57 ` [PATCH v6 2/3] s390: Implement arch_do_panic Mete Durlu
2026-08-31 9:57 ` [PATCH v6 3/3] sparc: " Mete Durlu
2026-09-01 0:19 ` 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=20260831171906.7520833ab8ac40d0369b0228@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=agordeev@linux.ibm.com \
--cc=andreas@gaisler.com \
--cc=borntraeger@linux.ibm.com \
--cc=davem@davemloft.net \
--cc=gor@linux.ibm.com \
--cc=hca@linux.ibm.com \
--cc=include@grrlz.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=meted@linux.ibm.com \
--cc=pmladek@suse.com \
--cc=sparclinux@vger.kernel.org \
--cc=svens@linux.ibm.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®