From: Christian Brauner <brauner@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Christian Brauner <brauner@kernel.org>,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [GIT PULL 06/12 for v6.18] rust
Date: Fri, 26 Sep 2025 16:19:00 +0200 [thread overview]
Message-ID: <20250926-vfs-rust-48d4952276a5@brauner> (raw)
In-Reply-To: <20250926-vfs-618-e880cf3b910f@brauner>
Hey Linus,
/* Summary */
This contains a few minor vfs rust changes:
* Add the pid namespace Rust wrappers to the correct MAINTAINERS entry.
* Use to_result() in the Rust file error handling code.
* Update imports for fs and pid_namespce Rust wrappers.
/* Testing */
gcc (Debian 14.2.0-19) 14.2.0
Debian clang version 19.1.7 (3+b1)
No build failures or warnings were observed.
/* Conflicts */
Merge conflicts with mainline
=============================
No known conflicts.
Merge conflicts with other trees
================================
No known conflicts.
The following changes since commit 8f5ae30d69d7543eee0d70083daf4de8fe15d585:
Linux 6.17-rc1 (2025-08-10 19:41:16 +0300)
are available in the Git repository at:
git@gitolite.kernel.org:pub/scm/linux/kernel/git/vfs/vfs tags/vfs-6.18-rc1.rust
for you to fetch changes up to c37adf34a5dc511e017b5a3bab15fe3171269e46:
rust: file: use to_result for error handling (2025-09-01 13:55:22 +0200)
Please consider pulling these changes from the signed vfs-6.18-rc1.rust tag.
Thanks!
Christian
----------------------------------------------------------------
vfs-6.18-rc1.rust
----------------------------------------------------------------
Alice Ryhl (1):
pid: add Rust files to MAINTAINERS
Onur Özkan (1):
rust: file: use to_result for error handling
Shankari Anand (2):
rust: pid_namespace: update AlwaysRefCounted imports from sync::aref
rust: fs: update ARef and AlwaysRefCounted imports from sync::aref
MAINTAINERS | 1 +
rust/kernel/fs/file.rs | 10 +++++-----
rust/kernel/pid_namespace.rs | 5 +----
3 files changed, 7 insertions(+), 9 deletions(-)
next prev parent reply other threads:[~2025-09-26 14:19 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-26 14:18 [GIT PULL 00/12 for v6.18] vfs 6.18 Christian Brauner
2025-09-26 14:18 ` [GIT PULL 01/12 for v6.18] misc Christian Brauner
2025-09-29 9:47 ` Christian Brauner
2025-09-29 19:31 ` pr-tracker-bot
2025-09-26 14:18 ` [GIT PULL 02/12 for v6.18] mount Christian Brauner
2025-09-29 19:31 ` pr-tracker-bot
2025-09-26 14:18 ` [GIT PULL 03/12 for v6.18] inode Christian Brauner
2025-09-29 19:31 ` pr-tracker-bot
2025-09-26 14:18 ` [GIT PULL 04/12 for v6.18] iomap Christian Brauner
2025-09-29 19:31 ` pr-tracker-bot
2025-09-26 14:18 ` [GIT PULL 05/12 for v6.18] pidfs Christian Brauner
2025-09-29 19:31 ` pr-tracker-bot
2025-10-01 14:18 ` Oleg Nesterov
2025-10-06 13:48 ` Christian Brauner
2025-10-07 14:34 ` Oleg Nesterov
2025-10-10 11:00 ` Christian Brauner
2025-09-26 14:19 ` Christian Brauner [this message]
2025-09-29 19:31 ` [GIT PULL 06/12 for v6.18] rust pr-tracker-bot
2025-09-26 14:19 ` [GIT PULL 07/12 for v6.18] workqueue Christian Brauner
2025-09-29 19:31 ` pr-tracker-bot
2025-09-26 14:19 ` [GIT PULL 08/12 for v6.18] core kernel Christian Brauner
2025-09-27 12:19 ` Sasha Levin
2025-09-29 9:53 ` Christian Brauner
2025-09-29 19:31 ` pr-tracker-bot
2025-09-26 14:19 ` [GIT PULL 9/12 for v6.18] afs Christian Brauner
2025-09-29 19:31 ` pr-tracker-bot
2025-09-26 14:19 ` [GIT PULL 10/12 for v6.18] namespaces Christian Brauner
2025-09-29 19:31 ` pr-tracker-bot
2025-09-26 14:19 ` [GIT PULL 11/12 for v6.18] writeback Christian Brauner
2025-09-29 19:31 ` pr-tracker-bot
2025-09-26 14:19 ` [GIT PULL 12/12 for v6.18] async directory preliminaries Christian Brauner
2025-09-29 19:31 ` 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=20250926-vfs-rust-48d4952276a5@brauner \
--to=brauner@kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).