All of lore.kernel.org
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Mete Durlu" <meted@linux.ibm.com>
Cc: "Vasily Gorbik" <gor@linux.ibm.com>,
	"Alexander Gordeev" <agordeev@linux.ibm.com>,
	linux-s390@vger.kernel.org, "Heiko Carstens" <hca@linux.ibm.com>,
	"Christian Borntraeger" <borntraeger@linux.ibm.com>
Subject: Re: [PATCH v6 1/3] panic: Introduce arch_do_panic
Date: Mon, 31 Aug 2026 10:07:32 +0000	[thread overview]
Message-ID: <20260831100733.0FA291F000E9@smtp.kernel.org> (raw)
In-Reply-To: <20260831-arch_do_panic-v6-1-a1e170a9e7fd@linux.ibm.com>

> Introduce a hook for architectures to put their specific panic handlers.
> s390 and sparc already has ifdef preprocessor checks to execute
> architecture specific code. Pave the way for vpanic() cleanup.
> 
> Reviewed-by: Bradley Morgan <include@grrlz.net>
> Suggested-by: Sven Schnelle <svens@linux.ibm.com>
> Signed-off-by: Mete Durlu <meted@linux.ibm.com>

Sashiko has reviewed this patch and found no issues. It looks great!

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20260831-arch_do_panic-v6-0-a1e170a9e7fd@linux.ibm.com?part=1


  reply	other threads:[~2026-08-31 10:07 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-31  9:57 [PATCH v6 0/3] Introduce arch_do_panic Mete Durlu
2026-08-31  9:57 ` [PATCH v6 1/3] panic: " Mete Durlu
2026-08-31 10:07   ` sashiko-bot [this message]
2026-08-31  9:57 ` [PATCH v6 2/3] s390: Implement arch_do_panic Mete Durlu
2026-08-31 10:14   ` sashiko-bot
2026-08-31  9:57 ` [PATCH v6 3/3] sparc: " Mete Durlu
2026-08-31 10:21   ` sashiko-bot
2026-09-01  0:19 ` [PATCH v6 0/3] Introduce arch_do_panic Andrew Morton
2026-10-07 12:54   ` Andreas Larsson

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=20260831100733.0FA291F000E9@smtp.kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=agordeev@linux.ibm.com \
    --cc=borntraeger@linux.ibm.com \
    --cc=gor@linux.ibm.com \
    --cc=hca@linux.ibm.com \
    --cc=linux-s390@vger.kernel.org \
    --cc=meted@linux.ibm.com \
    --cc=sashiko-reviews@lists.linux.dev \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.