All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+linux-soc@kernel.org
To: hasegawa-hitomi@fujitsu.com <hasegawa-hitomi@fujitsu.com>
Cc: soc@kernel.org
Subject: Re: [PATCH v5 0/1] soc: fujitsu: Add A64FX diagnostic interrupt driver
Date: Tue, 19 Jul 2022 14:10:15 +0000	[thread overview]
Message-ID: <165823981549.7750.3171524918425351359.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220520074119.3574753-1-hasegawa-hitomi@fujitsu.com>

Hello:

This patch was applied to soc/soc.git (for-next)
by Arnd Bergmann <arnd@arndb.de>:

On Fri, 20 May 2022 16:41:18 +0900 you wrote:
> The interrupt is set using pseudo-NMI if it is available. Arm has a
> diagnostic interrupt feature called "Arm Generic Diagnostic Dump and
> Reset device", but the A64FX does not support this feature and instead
> has its own device definition.
> 
> I tested on FX700:
> $ echo HARDLOCKUP > /sys/kernel/debug/provoke-crash/DIRECT
> [   86.259226] lkdtm: Performing direct entry HARDLOCKUP
> :
> :
> 
> [...]

Here is the summary with links:
  - [v5,1/1] soc: fujitsu: Add A64FX diagnostic interrupt driver
    https://git.kernel.org/soc/soc/c/64f89dfaa4f1

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2022-07-19 14:10 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-20  7:41 [PATCH v5 0/1] soc: fujitsu: Add A64FX diagnostic interrupt driver Hitomi Hasegawa
2022-05-20  7:41 ` Hitomi Hasegawa
2022-05-20  7:41 ` [PATCH v5 1/1] " Hitomi Hasegawa
2022-05-20  7:41   ` Hitomi Hasegawa
2022-06-09  7:48 ` [PATCH v5 0/1] " hasegawa-hitomi
2022-06-09  7:48   ` hasegawa-hitomi
2022-06-16  9:02 ` hasegawa-hitomi
2022-06-16  9:02   ` hasegawa-hitomi
2022-07-18 11:39   ` Arnd Bergmann
2022-07-18 11:39     ` Arnd Bergmann
2022-07-19 14:10 ` patchwork-bot+linux-soc [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=165823981549.7750.3171524918425351359.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+linux-soc@kernel.org \
    --cc=hasegawa-hitomi@fujitsu.com \
    --cc=soc@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.