From: Heiko Carstens <hca@linux.ibm.com>
To: Mete Durlu <meted@linux.ibm.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Petr Mladek <pmladek@suse.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>,
linux-kernel@vger.kernel.org, linux-s390@vger.kernel.org,
sparclinux@vger.kernel.org
Subject: Re: [PATCH v2 0/3] Introduce arch_do_panic
Date: Wed, 29 Jul 2026 14:06:24 +0200 [thread overview]
Message-ID: <20260729120624.61563A64-hca@linux.ibm.com> (raw)
In-Reply-To: <6213badb-436d-4e2f-a537-7171bde074f3@linux.ibm.com>
On Wed, Jul 29, 2026 at 12:48:49PM +0200, Mete Durlu wrote:
> On 29/07/2026 10:56, Heiko Carstens wrote:
> > On Mon, Jul 27, 2026 at 12:36:19PM +0200, Mete Durlu wrote:
> > Putting the define in a different header file per architecture doesn't
> > seem to be a good idea. There is no guarantee that this will work. So
> > either you find a common header file, where it is known that is (and
> > will be) included in panic.c, or you go with a weak function.
>
> I went over the headers included to panic.c, either they are really
> irrelevant or not present on other archs. To me the best candidate
> header seems like "asm/bug.h"
>
> $ find ./arch/ -name "bug.h" | grep include/asm | wc -l
> 16
>
> $ ls ./arch | wc -l
> 22 # actually 21 as we shouldn't count Kconfig file
>
> The architectures missing bug.h in their include/asm/ directory are
> hexagon, microblaze, nios2, um and xtensa
>
> I believe 16/21 is a good ratio but if this is still not good
> enough, I'd like to fallback to __weak implementation.
>
> What do you think Heiko?
Then go for __weak and wait if people shout at you :)
prev parent reply other threads:[~2026-07-29 12:06 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-27 10:36 [PATCH v2 0/3] Introduce arch_do_panic Mete Durlu
2026-07-27 10:36 ` [PATCH v2 1/3] panic: " Mete Durlu
2026-07-27 10:43 ` sashiko-bot
2026-07-27 12:59 ` Bradley Morgan
2026-07-28 10:13 ` Mete Durlu
2026-07-27 10:36 ` [PATCH v2 2/3] s390: Implement arch_do_panic Mete Durlu
2026-07-27 10:52 ` sashiko-bot
2026-07-27 13:01 ` Bradley Morgan
2026-07-28 10:43 ` Mete Durlu
2026-07-28 11:02 ` Bradley Morgan
2026-07-28 11:40 ` Sven Schnelle
2026-07-28 11:43 ` Bradley Morgan
2026-07-27 10:36 ` [PATCH v2 3/3] sparc: " Mete Durlu
2026-07-27 10:49 ` sashiko-bot
2026-07-27 13:02 ` Bradley Morgan
2026-07-29 8:56 ` [PATCH v2 0/3] Introduce arch_do_panic Heiko Carstens
2026-07-29 10:48 ` Mete Durlu
2026-07-29 12:06 ` Heiko Carstens [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=20260729120624.61563A64-hca@linux.ibm.com \
--to=hca@linux.ibm.com \
--cc=agordeev@linux.ibm.com \
--cc=akpm@linux-foundation.org \
--cc=andreas@gaisler.com \
--cc=borntraeger@linux.ibm.com \
--cc=davem@davemloft.net \
--cc=gor@linux.ibm.com \
--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