All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+linux-riscv@kernel.org
To: Alice Ryhl <aliceryhl@google.com>
Cc: linux-riscv@lists.infradead.org, rostedt@goodmis.org,
	mhiramat@kernel.org, mathieu.desnoyers@efficios.com,
	peterz@infradead.org, jpoimboe@kernel.org, jbaron@akamai.com,
	ardb@kernel.org, ojeda@kernel.org, alex.gaynor@gmail.com,
	wedsonaf@gmail.com, boqun.feng@gmail.com, gary@garyguo.net,
	bjorn3_gh@protonmail.com, benno.lossin@proton.me,
	a.hindborg@kernel.org, linux-trace-kernel@vger.kernel.org,
	rust-for-linux@vger.kernel.org, linux-kernel@vger.kernel.org,
	arnd@arndb.de, linux-arch@vger.kernel.org, tglx@linutronix.de,
	mingo@redhat.com, bp@alien8.de, dave.hansen@linux.intel.com,
	x86@kernel.org, hpa@zytor.com, seanjc@google.com,
	ubizjak@gmail.com, catalin.marinas@arm.com, will@kernel.org,
	maz@kernel.org, oliver.upton@linux.dev, mark.rutland@arm.com,
	ryan.roberts@arm.com, tabba@google.com,
	linux-arm-kernel@lists.infradead.org, paul.walmsley@sifive.com,
	palmer@dabbelt.com, aou@eecs.berkeley.edu,
	apatel@ventanamicro.com, ajones@ventanamicro.com,
	alexghiti@rivosinc.com, conor.dooley@microchip.com,
	samuel.holland@sifive.com, chenhuacai@kernel.org,
	kernel@xen0n.name, maobibo@loongson.cn, yangtiezhu@loongson.cn,
	akpm@linux-foundation.org, zhaotianrui@loongson.cn,
	loongarch@lists.linux.dev, cmllamas@google.com,
	palmer@rivosinc.com
Subject: Re: [PATCH v12 0/5] Tracepoints and static branch in Rust
Date: Wed, 11 Dec 2024 22:32:28 +0000	[thread overview]
Message-ID: <173395634899.1729195.7492083712432982213.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20241030-tracepoint-v12-0-eec7f0f8ad22@google.com>

Hello:

This series was applied to riscv/linux.git (fixes)
by Steven Rostedt (Google) <rostedt@goodmis.org>:

On Wed, 30 Oct 2024 16:04:23 +0000 you wrote:
> An important part of a production ready Linux kernel driver is
> tracepoints. So to write production ready Linux kernel drivers in Rust,
> we must be able to call tracepoints from Rust code. This patch series
> adds support for calling tracepoints declared in C from Rust.
> 
> This series includes a patch that adds a user of tracepoints to the
> rust_print sample. Please see that sample for details on what is needed
> to use this feature in Rust code.
> 
> [...]

Here is the summary with links:
  - [v12,1/5] rust: add static_branch_unlikely for static_key_false
    https://git.kernel.org/riscv/c/6e59bcc9c8ad
  - [v12,2/5] rust: add tracepoint support
    https://git.kernel.org/riscv/c/ad37bcd965fd
  - [v12,3/5] rust: samples: add tracepoint to Rust sample
    https://git.kernel.org/riscv/c/91d39024e1b0
  - [v12,4/5] jump_label: adjust inline asm to be consistent
    https://git.kernel.org/riscv/c/aecaf181651c
  - [v12,5/5] rust: add arch_static_branch
    https://git.kernel.org/riscv/c/169484ab6677

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: Alice Ryhl <aliceryhl@google.com>
Cc: linux-riscv@lists.infradead.org, rostedt@goodmis.org,
	mhiramat@kernel.org, mathieu.desnoyers@efficios.com,
	peterz@infradead.org, jpoimboe@kernel.org, jbaron@akamai.com,
	ardb@kernel.org, ojeda@kernel.org, alex.gaynor@gmail.com,
	wedsonaf@gmail.com, boqun.feng@gmail.com, gary@garyguo.net,
	bjorn3_gh@protonmail.com, benno.lossin@proton.me,
	a.hindborg@kernel.org, linux-trace-kernel@vger.kernel.org,
	rust-for-linux@vger.kernel.org, linux-kernel@vger.kernel.org,
	arnd@arndb.de, linux-arch@vger.kernel.org, tglx@linutronix.de,
	mingo@redhat.com, bp@alien8.de, dave.hansen@linux.intel.com,
	x86@kernel.org, hpa@zytor.com, seanjc@google.com,
	ubizjak@gmail.com, catalin.marinas@arm.com, will@kernel.org,
	maz@kernel.org, oliver.upton@linux.dev, mark.rutland@arm.com,
	ryan.roberts@arm.com, tabba@google.com,
	linux-arm-kernel@lists.infradead.org, paul.walmsley@sifive.com,
	palmer@dabbelt.com, aou@eecs.berkeley.edu,
	apatel@ventanamicro.com, ajones@ventanamicro.com,
	alexghiti@rivosinc.com, conor.dooley@microchip.com,
	samuel.holland@sifive.com, chenhuacai@kernel.org,
	kernel@xen0n.name, maobibo@loongson.cn, yangtiezhu@loongson.cn,
	akpm@linux-foundation.org, zhaotianrui@loongson.cn,
	loongarch@lists.linux.dev, cmllamas@google.com,
	palmer@rivosinc.com
Subject: Re: [PATCH v12 0/5] Tracepoints and static branch in Rust
Date: Wed, 11 Dec 2024 22:32:28 +0000	[thread overview]
Message-ID: <173395634899.1729195.7492083712432982213.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20241030-tracepoint-v12-0-eec7f0f8ad22@google.com>

Hello:

This series was applied to riscv/linux.git (fixes)
by Steven Rostedt (Google) <rostedt@goodmis.org>:

On Wed, 30 Oct 2024 16:04:23 +0000 you wrote:
> An important part of a production ready Linux kernel driver is
> tracepoints. So to write production ready Linux kernel drivers in Rust,
> we must be able to call tracepoints from Rust code. This patch series
> adds support for calling tracepoints declared in C from Rust.
> 
> This series includes a patch that adds a user of tracepoints to the
> rust_print sample. Please see that sample for details on what is needed
> to use this feature in Rust code.
> 
> [...]

Here is the summary with links:
  - [v12,1/5] rust: add static_branch_unlikely for static_key_false
    https://git.kernel.org/riscv/c/6e59bcc9c8ad
  - [v12,2/5] rust: add tracepoint support
    https://git.kernel.org/riscv/c/ad37bcd965fd
  - [v12,3/5] rust: samples: add tracepoint to Rust sample
    https://git.kernel.org/riscv/c/91d39024e1b0
  - [v12,4/5] jump_label: adjust inline asm to be consistent
    https://git.kernel.org/riscv/c/aecaf181651c
  - [v12,5/5] rust: add arch_static_branch
    https://git.kernel.org/riscv/c/169484ab6677

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:32 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-30 16:04 [PATCH v12 0/5] Tracepoints and static branch in Rust Alice Ryhl
2024-10-30 16:04 ` Alice Ryhl
2024-10-30 16:04 ` [PATCH v12 1/5] rust: add static_branch_unlikely for static_key_false Alice Ryhl
2024-10-30 16:04   ` Alice Ryhl
2024-10-30 16:04 ` [PATCH v12 2/5] rust: add tracepoint support Alice Ryhl
2024-10-30 16:04   ` Alice Ryhl
2024-10-30 16:04 ` [PATCH v12 3/5] rust: samples: add tracepoint to Rust sample Alice Ryhl
2024-10-30 16:04   ` Alice Ryhl
2024-11-02  7:07   ` kernel test robot
2024-11-04 10:13     ` Alice Ryhl
2024-10-30 16:04 ` [PATCH v12 4/5] jump_label: adjust inline asm to be consistent Alice Ryhl
2024-10-30 16:04   ` Alice Ryhl
2024-10-30 23:13   ` Steven Rostedt
2024-10-30 23:13     ` Steven Rostedt
2024-10-31  0:10     ` Russell King (Oracle)
2024-10-31  0:10       ` Russell King (Oracle)
2024-10-31  0:14       ` Steven Rostedt
2024-10-31  0:14         ` Steven Rostedt
2024-10-30 16:04 ` [PATCH v12 5/5] rust: add arch_static_branch Alice Ryhl
2024-10-30 16:04   ` Alice Ryhl
2024-12-11 22:32 ` patchwork-bot+linux-riscv [this message]
2024-12-11 22:32   ` [PATCH v12 0/5] Tracepoints and static branch in Rust patchwork-bot+linux-riscv
2024-12-12 12:40   ` Miguel Ojeda
2024-12-12 12:40     ` Miguel Ojeda

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=173395634899.1729195.7492083712432982213.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+linux-riscv@kernel.org \
    --cc=a.hindborg@kernel.org \
    --cc=ajones@ventanamicro.com \
    --cc=akpm@linux-foundation.org \
    --cc=alex.gaynor@gmail.com \
    --cc=alexghiti@rivosinc.com \
    --cc=aliceryhl@google.com \
    --cc=aou@eecs.berkeley.edu \
    --cc=apatel@ventanamicro.com \
    --cc=ardb@kernel.org \
    --cc=arnd@arndb.de \
    --cc=benno.lossin@proton.me \
    --cc=bjorn3_gh@protonmail.com \
    --cc=boqun.feng@gmail.com \
    --cc=bp@alien8.de \
    --cc=catalin.marinas@arm.com \
    --cc=chenhuacai@kernel.org \
    --cc=cmllamas@google.com \
    --cc=conor.dooley@microchip.com \
    --cc=dave.hansen@linux.intel.com \
    --cc=gary@garyguo.net \
    --cc=hpa@zytor.com \
    --cc=jbaron@akamai.com \
    --cc=jpoimboe@kernel.org \
    --cc=kernel@xen0n.name \
    --cc=linux-arch@vger.kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=linux-trace-kernel@vger.kernel.org \
    --cc=loongarch@lists.linux.dev \
    --cc=maobibo@loongson.cn \
    --cc=mark.rutland@arm.com \
    --cc=mathieu.desnoyers@efficios.com \
    --cc=maz@kernel.org \
    --cc=mhiramat@kernel.org \
    --cc=mingo@redhat.com \
    --cc=ojeda@kernel.org \
    --cc=oliver.upton@linux.dev \
    --cc=palmer@dabbelt.com \
    --cc=palmer@rivosinc.com \
    --cc=paul.walmsley@sifive.com \
    --cc=peterz@infradead.org \
    --cc=rostedt@goodmis.org \
    --cc=rust-for-linux@vger.kernel.org \
    --cc=ryan.roberts@arm.com \
    --cc=samuel.holland@sifive.com \
    --cc=seanjc@google.com \
    --cc=tabba@google.com \
    --cc=tglx@linutronix.de \
    --cc=ubizjak@gmail.com \
    --cc=wedsonaf@gmail.com \
    --cc=will@kernel.org \
    --cc=x86@kernel.org \
    --cc=yangtiezhu@loongson.cn \
    --cc=zhaotianrui@loongson.cn \
    /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.