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] vfs rust
Date: Sat, 22 Mar 2025 11:17:35 +0100 [thread overview]
Message-ID: <20250322-vfs-rust-22efd627df4b@brauner> (raw)
Hey Linus,
/* Summary */
This contains minor fixes and improvements to rust file bindings:
- Optimize rust symbol generation for FileDescriptorReservation.
- Optimize rust symbol generation for SeqFile.
/* Testing */
gcc version 14.2.0 (Debian 14.2.0-6)
Debian clang version 16.0.6 (27+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 2014c95afecee3e76ca4a56956a936e23283f05b:
Linux 6.14-rc1 (2025-02-02 15:39:26 -0800)
are available in the Git repository at:
git@gitolite.kernel.org:pub/scm/linux/kernel/git/vfs/vfs tags/vfs-6.15-rc1.rust
for you to fetch changes up to 0b9817caac1d4d6bf7dc8f7f23ffd95a3f5bb43a:
rust: optimize rust symbol generation for SeqFile (2025-03-18 09:26:24 +0100)
Please consider pulling these changes from the signed vfs-6.15-rc1.rust tag.
Thanks!
Christian
----------------------------------------------------------------
vfs-6.15-rc1.rust
----------------------------------------------------------------
Kunwu Chan (2):
rust: file: optimize rust symbol generation for FileDescriptorReservation
rust: optimize rust symbol generation for SeqFile
rust/kernel/fs/file.rs | 4 ++++
rust/kernel/seq_file.rs | 1 +
2 files changed, 5 insertions(+)
next reply other threads:[~2025-03-22 10:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-22 10:17 Christian Brauner [this message]
2025-03-24 21:01 ` [GIT PULL] vfs rust 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=20250322-vfs-rust-22efd627df4b@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).