From: "tip-bot2 for Boqun Feng" <tip-bot2@linutronix.de>
To: linux-tip-commits@vger.kernel.org
Cc: Boqun Feng <boqun.feng@gmail.com>,
Thomas Gleixner <tglx@linutronix.de>,
Alice Ryhl <aliceryhl@google.com>,
Miguel Ojeda <ojeda@kernel.org>,
x86@kernel.org, linux-kernel@vger.kernel.org
Subject: [tip: timers/core] rust: time: doc: Add missing C header links
Date: Tue, 30 Apr 2024 22:10:10 -0000 [thread overview]
Message-ID: <171451501055.10875.16648047643476083892.tip-bot2@tip-bot2> (raw)
In-Reply-To: <20240411230801.1504496-2-boqun.feng@gmail.com>
The following commit has been merged into the timers/core branch of tip:
Commit-ID: ddd9120983c3efbcaa3a4c7777da1440f8ce27d8
Gitweb: https://git.kernel.org/tip/ddd9120983c3efbcaa3a4c7777da1440f8ce27d8
Author: Boqun Feng <boqun.feng@gmail.com>
AuthorDate: Thu, 11 Apr 2024 16:08:00 -07:00
Committer: Thomas Gleixner <tglx@linutronix.de>
CommitterDate: Wed, 01 May 2024 00:04:47 +02:00
rust: time: doc: Add missing C header links
The definitions related to jiffies are at linux/jiffies.h, and the
definitions related to ktime_t are at linux/ktime.h, since
`kernel::time` provides the functionality dealing with jiffies and
ktime_t, it makes sense to add links to them from Rust's time module.
Signed-off-by: Boqun Feng <boqun.feng@gmail.com>
Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
Reviewed-by: Alice Ryhl <aliceryhl@google.com>
Acked-by: Miguel Ojeda <ojeda@kernel.org>
Link: https://lore.kernel.org/r/20240411230801.1504496-2-boqun.feng@gmail.com
---
rust/kernel/time.rs | 3 +++
1 file changed, 3 insertions(+)
diff --git a/rust/kernel/time.rs b/rust/kernel/time.rs
index 6811d5c..e3bb5e8 100644
--- a/rust/kernel/time.rs
+++ b/rust/kernel/time.rs
@@ -4,6 +4,9 @@
//!
//! This module contains the kernel APIs related to time and timers that
//! have been ported or wrapped for usage by Rust code in the kernel.
+//!
+//! C header: [`include/linux/jiffies.h`](srctree/include/linux/jiffies.h).
+//! C header: [`include/linux/ktime.h`](srctree/include/linux/ktime.h).
/// The number of nanoseconds per millisecond.
pub const NSEC_PER_MSEC: i64 = bindings::NSEC_PER_MSEC as i64;
next prev parent reply other threads:[~2024-04-30 22:10 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-11 23:07 [PATCH 0/2] rust: time related cleanup Boqun Feng
2024-04-11 23:08 ` [PATCH 1/2] rust: time: doc: Add missing C header links Boqun Feng
2024-04-12 7:15 ` Miguel Ojeda
2024-04-12 11:04 ` Alice Ryhl
2024-04-30 22:10 ` tip-bot2 for Boqun Feng [this message]
2024-04-11 23:08 ` [PATCH 2/2] rust: time: Use wrapping_sub() for Ktime::sub() Boqun Feng
2024-04-12 7:14 ` Miguel Ojeda
2024-04-12 7:43 ` Philipp Stanner
2024-04-12 7:58 ` Miguel Ojeda
2024-04-15 17:08 ` Kees Cook
2024-04-12 13:34 ` Boqun Feng
2024-04-12 14:41 ` Miguel Ojeda
2024-04-13 1:30 ` Boqun Feng
2024-04-13 2:16 ` Miguel Ojeda
2024-04-12 8:36 ` Alice Ryhl
2024-04-12 13:18 ` Boqun Feng
2024-04-12 13:51 ` Alice Ryhl
2024-04-25 9:00 ` Andreas Hindborg
2024-04-25 14:28 ` Boqun Feng
2024-04-23 21:11 ` Boqun Feng
2024-04-23 23:37 ` Kees Cook
2024-04-24 10:21 ` Miguel Ojeda
2024-05-09 12:14 ` Thomas Gleixner
2024-05-13 14:06 ` Boqun Feng
2024-05-13 15:04 ` Miguel Ojeda
2024-05-14 13:12 ` Boqun Feng
2024-05-14 14:21 ` 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=171451501055.10875.16648047643476083892.tip-bot2@tip-bot2 \
--to=tip-bot2@linutronix.de \
--cc=aliceryhl@google.com \
--cc=boqun.feng@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=ojeda@kernel.org \
--cc=tglx@linutronix.de \
--cc=x86@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 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®