All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+linux-riscv@kernel.org
To: =?utf-8?b?QmrDtnJuIFTDtnBlbCA8Ympvcm5Aa2VybmVsLm9yZz4=?=@ci.codeaurora.org
Cc: linux-riscv@lists.infradead.org, paul.walmsley@sifive.com,
	palmer@dabbelt.com, aou@eecs.berkeley.edu, bjorn@rivosinc.com,
	schwab@linux-m68k.org, geert@linux-m68k.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 0/2] riscv: Dump faulting instructions in oops handler
Date: Wed, 22 Feb 2023 15:00:22 +0000	[thread overview]
Message-ID: <167707802237.24438.17153104207129769364.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230119074738.708301-1-bjorn@kernel.org>

Hello:

This series was applied to riscv/linux.git (for-next)
by Palmer Dabbelt <palmer@rivosinc.com>:

On Thu, 19 Jan 2023 08:47:36 +0100 you wrote:
> From: Björn Töpel <bjorn@rivosinc.com>
> 
> RISC-V does not dump faulting instructions in the oops handler. This
> series adds "Code:" dumps to the oops output together with
> scripts/decodecode support.
> 
> Thanks,
> Björn
> 
> [...]

Here is the summary with links:
  - [v3,1/2] riscv: Add instruction dump to RISC-V splats
    https://git.kernel.org/riscv/c/eb165bfa8eaf
  - [v3,2/2] scripts/decodecode: Add support for RISC-V
    https://git.kernel.org/riscv/c/00b242509c8f

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



_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv

WARNING: multiple messages have this Message-ID (diff)
From: patchwork-bot+linux-riscv@kernel.org
To: =?utf-8?b?QmrDtnJuIFTDtnBlbCA8Ympvcm5Aa2VybmVsLm9yZz4=?=@ci.codeaurora.org
Cc: linux-riscv@lists.infradead.org, paul.walmsley@sifive.com,
	palmer@dabbelt.com, aou@eecs.berkeley.edu, bjorn@rivosinc.com,
	schwab@linux-m68k.org, geert@linux-m68k.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 0/2] riscv: Dump faulting instructions in oops handler
Date: Wed, 22 Feb 2023 15:00:22 +0000	[thread overview]
Message-ID: <167707802237.24438.17153104207129769364.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230119074738.708301-1-bjorn@kernel.org>

Hello:

This series was applied to riscv/linux.git (for-next)
by Palmer Dabbelt <palmer@rivosinc.com>:

On Thu, 19 Jan 2023 08:47:36 +0100 you wrote:
> From: Björn Töpel <bjorn@rivosinc.com>
> 
> RISC-V does not dump faulting instructions in the oops handler. This
> series adds "Code:" dumps to the oops output together with
> scripts/decodecode support.
> 
> Thanks,
> Björn
> 
> [...]

Here is the summary with links:
  - [v3,1/2] riscv: Add instruction dump to RISC-V splats
    https://git.kernel.org/riscv/c/eb165bfa8eaf
  - [v3,2/2] scripts/decodecode: Add support for RISC-V
    https://git.kernel.org/riscv/c/00b242509c8f

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



  parent reply	other threads:[~2023-02-22 15:00 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-19  7:47 [PATCH v3 0/2] riscv: Dump faulting instructions in oops handler Björn Töpel
2023-01-19  7:47 ` Björn Töpel
2023-01-19  7:47 ` [PATCH v3 1/2] riscv: Add instruction dump to RISC-V splats Björn Töpel
2023-01-19  7:47   ` Björn Töpel
2023-01-19  7:47 ` [PATCH v3 2/2] scripts/decodecode: Add support for RISC-V Björn Töpel
2023-01-19  7:47   ` Björn Töpel
2023-02-21 15:18   ` Alexandre Ghiti
2023-02-21 15:18     ` Alexandre Ghiti
2023-02-22 15:00 ` patchwork-bot+linux-riscv [this message]
2023-02-22 15:00   ` [PATCH v3 0/2] riscv: Dump faulting instructions in oops handler patchwork-bot+linux-riscv

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=167707802237.24438.17153104207129769364.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+linux-riscv@kernel.org \
    --cc==?utf-8?b?QmrDtnJuIFTDtnBlbCA8Ympvcm5Aa2VybmVsLm9yZz4=?=@ci.codeaurora.org \
    --cc=aou@eecs.berkeley.edu \
    --cc=bjorn@rivosinc.com \
    --cc=geert@linux-m68k.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=palmer@dabbelt.com \
    --cc=paul.walmsley@sifive.com \
    --cc=schwab@linux-m68k.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.