From: Tejun Heo <tj@kernel.org>
To: torvalds@linux-foundation.org
Cc: jiangshanlai@gmail.com, linux-kernel@vger.kernel.org,
aliceryhl@google.com
Subject: [GIT PULL] workqueue rust bindings for v6.7
Date: Mon, 30 Oct 2023 14:46:58 -1000 [thread overview]
Message-ID: <ZUBOgm4uS5t0-qV3@slm.duckdns.org> (raw)
The following changes since commit 6465e260f48790807eef06b583b38ca9789b6072:
Linux 6.6-rc3 (2023-09-24 14:31:13 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/tj/wq.git/ tags/wq-for-6.7-rust-bindings
for you to fetch changes up to 15b286d1fd056b0366bc8d211ff2c4ce2449eacb:
rust: workqueue: add examples (2023-09-25 09:46:42 -1000)
----------------------------------------------------------------
workqueue: Add rust bindings for v6.7
to allow rust code to schedule work items on workqueues. While the current
bindings don't cover all of the workqueue API, it provides enough for basic
usage and can be expanded as needed.
----------------------------------------------------------------
Alice Ryhl (5):
rust: workqueue: add low-level workqueue bindings
rust: workqueue: add helper for defining work_struct fields
rust: workqueue: implement `WorkItemPointer` for pointer types
rust: workqueue: add `try_spawn` helper method
rust: workqueue: add examples
Wedson Almeida Filho (2):
rust: sync: add `Arc::{from_raw, into_raw}`
rust: workqueue: define built-in queues
rust/bindings/bindings_helper.h | 1 +
rust/helpers.c | 13 +
rust/kernel/lib.rs | 3 +
rust/kernel/sync/arc.rs | 46 ++-
rust/kernel/workqueue.rs | 679 ++++++++++++++++++++++++++++++++++++++++
scripts/Makefile.build | 2 +-
6 files changed, 741 insertions(+), 3 deletions(-)
create mode 100644 rust/kernel/workqueue.rs
--
tejun
next reply other threads:[~2023-10-31 0:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-31 0:46 Tejun Heo [this message]
2023-10-31 7:02 ` pr-tracker-bot
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=ZUBOgm4uS5t0-qV3@slm.duckdns.org \
--to=tj@kernel.org \
--cc=aliceryhl@google.com \
--cc=jiangshanlai@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®