From: "gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>
To: "hasegawa-hitomi@fujitsu.com" <hasegawa-hitomi@fujitsu.com>
Cc: Daniel Thompson <daniel.thompson@linaro.org>,
Arnd Bergmann <arnd@arndb.de>,
Linux ARM <linux-arm-kernel@lists.infradead.org>,
SoC Team <soc@kernel.org>,
"open list:SERIAL DRIVERS" <linux-serial@vger.kernel.org>,
Sumit Garg <sumit.garg@linaro.org>,
Olof Johansson <olof@lixom.net>,
Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will@kernel.org>, Jiri Slaby <jirislaby@kernel.org>,
Jason Wessel <jason.wessel@windriver.com>,
Doug Anderson <dianders@chromium.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
"kgdb-bugreport@lists.sourceforge.net"
<kgdb-bugreport@lists.sourceforge.net>,
Peter Zijlstra <peterz@infradead.org>,
Mike Travis <mike.travis@hpe.com>
Subject: Re: [PATCH v3 1/1] soc: fujitsu: Add A64FX diagnostic interrupt driver
Date: Thu, 28 Apr 2022 07:45:26 +0200 [thread overview]
Message-ID: <Ymop9jwBWGioF0Da@kroah.com> (raw)
In-Reply-To: <OSZPR01MB70504BD8347355EB51F7CCB8EBFD9@OSZPR01MB7050.jpnprd01.prod.outlook.com>
On Thu, Apr 28, 2022 at 02:15:52AM +0000, hasegawa-hitomi@fujitsu.com wrote:
> Hi Greg, Arnd, and Daniel,
>
> > I understand that it is not appropriate to hardcode c.
> > How about using __setup() to add a new kernel parameter and allow the admin
> > to specify the sysrq command when booting?
>
> I have received a lot of advice regarding sysrq, but after some consideration,
> I would like to change to calling panic() directly as in v1 instead of sysrq.
panic() seems good to me!
WARNING: multiple messages have this Message-ID (diff)
From: "gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>
To: "hasegawa-hitomi@fujitsu.com" <hasegawa-hitomi@fujitsu.com>
Cc: Daniel Thompson <daniel.thompson@linaro.org>,
Arnd Bergmann <arnd@arndb.de>,
Linux ARM <linux-arm-kernel@lists.infradead.org>,
SoC Team <soc@kernel.org>,
"open list:SERIAL DRIVERS" <linux-serial@vger.kernel.org>,
Sumit Garg <sumit.garg@linaro.org>,
Olof Johansson <olof@lixom.net>,
Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will@kernel.org>, Jiri Slaby <jirislaby@kernel.org>,
Jason Wessel <jason.wessel@windriver.com>,
Doug Anderson <dianders@chromium.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
"kgdb-bugreport@lists.sourceforge.net"
<kgdb-bugreport@lists.sourceforge.net>,
Peter Zijlstra <peterz@infradead.org>,
Mike Travis <mike.travis@hpe.com>
Subject: Re: [PATCH v3 1/1] soc: fujitsu: Add A64FX diagnostic interrupt driver
Date: Thu, 28 Apr 2022 07:45:26 +0200 [thread overview]
Message-ID: <Ymop9jwBWGioF0Da@kroah.com> (raw)
In-Reply-To: <OSZPR01MB70504BD8347355EB51F7CCB8EBFD9@OSZPR01MB7050.jpnprd01.prod.outlook.com>
On Thu, Apr 28, 2022 at 02:15:52AM +0000, hasegawa-hitomi@fujitsu.com wrote:
> Hi Greg, Arnd, and Daniel,
>
> > I understand that it is not appropriate to hardcode c.
> > How about using __setup() to add a new kernel parameter and allow the admin
> > to specify the sysrq command when booting?
>
> I have received a lot of advice regarding sysrq, but after some consideration,
> I would like to change to calling panic() directly as in v1 instead of sysrq.
panic() seems good to me!
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2022-04-28 5:45 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-31 9:22 [PATCH v3 0/1] soc: fujitsu: Add A64FX diagnostic interrupt driver Hitomi Hasegawa
2022-03-31 9:22 ` Hitomi Hasegawa
2022-03-31 9:22 ` [PATCH v3 1/1] " Hitomi Hasegawa
2022-03-31 9:22 ` Hitomi Hasegawa
2022-03-31 11:49 ` Greg KH
2022-03-31 11:49 ` Greg KH
2022-03-31 15:44 ` Arnd Bergmann
2022-03-31 15:44 ` Arnd Bergmann
2022-04-08 13:32 ` Daniel Thompson
2022-04-08 13:32 ` Daniel Thompson
2022-04-08 14:17 ` Arnd Bergmann
2022-04-08 14:17 ` Arnd Bergmann
2022-04-08 14:21 ` Greg KH
2022-04-08 14:21 ` Greg KH
2022-04-08 14:49 ` Arnd Bergmann
2022-04-08 14:49 ` Arnd Bergmann
2022-04-08 14:59 ` Greg KH
2022-04-08 14:59 ` Greg KH
2022-04-08 15:02 ` Daniel Thompson
2022-04-08 15:02 ` Daniel Thompson
2022-04-19 8:36 ` hasegawa-hitomi
2022-04-19 8:36 ` hasegawa-hitomi
2022-04-28 2:15 ` hasegawa-hitomi
2022-04-28 2:15 ` hasegawa-hitomi
2022-04-28 5:45 ` gregkh [this message]
2022-04-28 5:45 ` gregkh
2022-04-28 7:04 ` Arnd Bergmann
2022-04-28 7:04 ` Arnd Bergmann
2022-04-08 10:32 ` hasegawa-hitomi
2022-04-08 10:32 ` hasegawa-hitomi
2022-04-08 10:44 ` Itaru Kitayama
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=Ymop9jwBWGioF0Da@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=arnd@arndb.de \
--cc=catalin.marinas@arm.com \
--cc=daniel.thompson@linaro.org \
--cc=dianders@chromium.org \
--cc=hasegawa-hitomi@fujitsu.com \
--cc=jason.wessel@windriver.com \
--cc=jirislaby@kernel.org \
--cc=kgdb-bugreport@lists.sourceforge.net \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=mike.travis@hpe.com \
--cc=olof@lixom.net \
--cc=peterz@infradead.org \
--cc=soc@kernel.org \
--cc=sumit.garg@linaro.org \
--cc=will@kernel.org \
/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.