All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andreas Hindborg <a.hindborg@kernel.org>
To: Breno Leitao <leitao@debian.org>
Cc: linux-kernel@vger.kernel.org, rust-for-linux@vger.kernel.org
Subject: [GIT PULL] Rust configfs changes for v7.4-rc1
Date: Wed, 07 Oct 2026 16:12:27 +0200	[thread overview]
Message-ID: <87a4opeh10.fsf@kernel.org> (raw)

Hi Breno,

Here is the first pull request from me to you for the Rust configfs
abstractions. Please note that I neglected to push these three patches
to the remote that is picked up by linux-next (just did it now).
However, I tried the merge and verified everything works under my usual
configurations, so we should be fine.

Best regards,
Andreas Hindborg


The following changes since commit df2908090cda368b01ff43709f51890076c56157:

  Linux 7.3-rc2 (2026-09-06 15:07:20 -0700)

are available in the Git repository at:

  https://git.kernel.org/pub/scm/linux/kernel/git/a.hindborg/linux.git tags/rust-configfs-for-v7.4-rc1

for you to fetch changes up to e84c9b64df615e658e47561b835c1364dc48f0c0:

  rust: configfs: fix data offset calculation for subsystem callbacks (2026-09-29 10:30:08 +0200)

----------------------------------------------------------------
Rust configfs changes for v7.4-rc1

Three changes for the Rust configfs bindings. One typo fix for a safety comment and two bug fixes.

----------------------------------------------------------------
Andreas Hindborg (1):
      rust: configfs: fix data offset calculation for subsystem callbacks

Yilin Chen (2):
      rust: configfs: fix release safety documentation
      rust: configfs: require thread-safe callback data

 rust/kernel/configfs.rs | 110 ++++++++++++++++++++++++++++++++----------------
 1 file changed, 74 insertions(+), 36 deletions(-)


                 reply	other threads:[~2026-10-07 14:12 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=87a4opeh10.fsf@kernel.org \
    --to=a.hindborg@kernel.org \
    --cc=leitao@debian.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rust-for-linux@vger.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.