All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+linux-riscv@kernel.org
To: =?utf-8?b?QmrDtnJuIFTDtnBlbCA8Ympvcm5Aa2VybmVsLm9yZz4=?=@aws-us-west-2-korg-oddjob-rhel9-1.codeaurora.org
Cc: linux-riscv@lists.infradead.org, peterz@infradead.org,
	mingo@redhat.com, acme@kernel.org, namhyung@kernel.org,
	mark.rutland@arm.com, alexander.shishkin@linux.intel.com,
	jolsa@kernel.org, irogers@google.com, adrian.hunter@intel.com,
	kan.liang@linux.intel.com, linux-kernel@vger.kernel.org,
	linux-perf-users@vger.kernel.org, bjorn@rivosinc.com,
	paul.walmsley@sifive.com, palmer@dabbelt.com,
	aou@eecs.berkeley.edu, anup@brainfault.org, atishp@rivosinc.com
Subject: Re: [PATCH] perf, riscv: Wire up perf trace support for RISC-V
Date: Wed, 11 Dec 2024 22:33:21 +0000	[thread overview]
Message-ID: <173395640149.1729195.11467040098314252452.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20241024190353.46737-1-bjorn@kernel.org>

Hello:

This patch was applied to riscv/linux.git (fixes)
by Namhyung Kim <namhyung@kernel.org>:

On Thu, 24 Oct 2024 12:03:51 -0700 you wrote:
> From: Björn Töpel <bjorn@rivosinc.com>
> 
> RISC-V does not currently support perf trace, since the system call
> table is not generated.
> 
> Perform the copy/paste exercise, wiring up RISC-V system call table
> generation.
> 
> [...]

Here is the summary with links:
  - perf, riscv: Wire up perf trace support for RISC-V
    https://git.kernel.org/riscv/c/8c0d1202bad3

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



WARNING: multiple messages have this Message-ID (diff)
From: patchwork-bot+linux-riscv@kernel.org
To: =?utf-8?b?QmrDtnJuIFTDtnBlbCA8Ympvcm5Aa2VybmVsLm9yZz4=?=@aws-us-west-2-korg-oddjob-rhel9-1.codeaurora.org
Cc: linux-riscv@lists.infradead.org, peterz@infradead.org,
	mingo@redhat.com, acme@kernel.org, namhyung@kernel.org,
	mark.rutland@arm.com, alexander.shishkin@linux.intel.com,
	jolsa@kernel.org, irogers@google.com, adrian.hunter@intel.com,
	kan.liang@linux.intel.com, linux-kernel@vger.kernel.org,
	linux-perf-users@vger.kernel.org, bjorn@rivosinc.com,
	paul.walmsley@sifive.com, palmer@dabbelt.com,
	aou@eecs.berkeley.edu, anup@brainfault.org, atishp@rivosinc.com
Subject: Re: [PATCH] perf, riscv: Wire up perf trace support for RISC-V
Date: Wed, 11 Dec 2024 22:33:21 +0000	[thread overview]
Message-ID: <173395640149.1729195.11467040098314252452.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20241024190353.46737-1-bjorn@kernel.org>

Hello:

This patch was applied to riscv/linux.git (fixes)
by Namhyung Kim <namhyung@kernel.org>:

On Thu, 24 Oct 2024 12:03:51 -0700 you wrote:
> From: Björn Töpel <bjorn@rivosinc.com>
> 
> RISC-V does not currently support perf trace, since the system call
> table is not generated.
> 
> Perform the copy/paste exercise, wiring up RISC-V system call table
> generation.
> 
> [...]

Here is the summary with links:
  - perf, riscv: Wire up perf trace support for RISC-V
    https://git.kernel.org/riscv/c/8c0d1202bad3

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

  parent reply	other threads:[~2024-12-11 22:33 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-24 19:03 [PATCH] perf, riscv: Wire up perf trace support for RISC-V Björn Töpel
2024-10-24 19:03 ` Björn Töpel
2024-10-30  0:37 ` Namhyung Kim
2024-10-30  0:37   ` Namhyung Kim
2024-10-30  7:31   ` Alexandre Ghiti
2024-10-30  7:31     ` Alexandre Ghiti
2024-10-31  6:39     ` Namhyung Kim
2024-10-31  6:39       ` Namhyung Kim
2024-10-31 17:12 ` Namhyung Kim
2024-10-31 17:12   ` Namhyung Kim
2024-12-11 22:33 ` patchwork-bot+linux-riscv [this message]
2024-12-11 22:33   ` 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=173395640149.1729195.11467040098314252452.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+linux-riscv@kernel.org \
    --cc==?utf-8?b?QmrDtnJuIFTDtnBlbCA8Ympvcm5Aa2VybmVsLm9yZz4=?=@aws-us-west-2-korg-oddjob-rhel9-1.codeaurora.org \
    --cc=acme@kernel.org \
    --cc=adrian.hunter@intel.com \
    --cc=alexander.shishkin@linux.intel.com \
    --cc=anup@brainfault.org \
    --cc=aou@eecs.berkeley.edu \
    --cc=atishp@rivosinc.com \
    --cc=bjorn@rivosinc.com \
    --cc=irogers@google.com \
    --cc=jolsa@kernel.org \
    --cc=kan.liang@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-perf-users@vger.kernel.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=mark.rutland@arm.com \
    --cc=mingo@redhat.com \
    --cc=namhyung@kernel.org \
    --cc=palmer@dabbelt.com \
    --cc=paul.walmsley@sifive.com \
    --cc=peterz@infradead.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.