From: Timur Tabi <ttabi@nvidia.com>
To: "tmgross@umich.edu" <tmgross@umich.edu>,
"bjorn3_gh@protonmail.com" <bjorn3_gh@protonmail.com>,
"benno.lossin@proton.me" <benno.lossin@proton.me>,
John Hubbard <jhubbard@nvidia.com>,
"gary@garyguo.net" <gary@garyguo.net>,
"a.hindborg@kernel.org" <a.hindborg@kernel.org>,
"simona@ffwll.ch" <simona@ffwll.ch>,
"airlied@gmail.com" <airlied@gmail.com>,
"boqun.feng@gmail.com" <boqun.feng@gmail.com>,
"dakr@kernel.org" <dakr@kernel.org>,
"alex.gaynor@gmail.com" <alex.gaynor@gmail.com>,
"aliceryhl@google.com" <aliceryhl@google.com>,
Ben Skeggs <bskeggs@nvidia.com>,
Alexandre Courbot <acourbot@nvidia.com>,
"ojeda@kernel.org" <ojeda@kernel.org>
Cc: "dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>,
"nouveau@lists.freedesktop.org" <nouveau@lists.freedesktop.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"rust-for-linux@vger.kernel.org" <rust-for-linux@vger.kernel.org>
Subject: Re: [PATCH RFC v2 1/5] rust: add useful ops for u64
Date: Mon, 10 Mar 2025 20:46:43 +0000 [thread overview]
Message-ID: <ab9b34381f6d5889e978bef352b923455b475ae6.camel@nvidia.com> (raw)
In-Reply-To: <20250304-nova_timer-v2-1-8fb13f3f8cff@nvidia.com>
On Tue, 2025-03-04 at 22:53 +0900, Alexandre Courbot wrote:
> +/// Useful operations for `u64`.
> +pub trait U64Ext {
> + /// Build a `u64` by combining its `high` and `low` parts.
> + ///
> + /// ```
> + /// use kernel::num::U64Ext;
> + /// assert_eq!(u64::from_u32s(0x01234567, 0x89abcdef),
> 0x01234567_89abcdef);
> + /// ```
> + fn from_u32s(high: u32, low: u32) -> Self;
> +
> + fn upper_32_bits(self) -> u32;
> + fn lower_32_bits(self) -> u32;
> +}
This generates a few warnings when I build it:
RUSTC L rust/kernel.o
warning: missing documentation for a method
--> rust/kernel/num.rs:15:5
|
15 | fn upper_32_bits(self) -> u32;
| ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
|
= note: requested on the command line with `-W missing-docs`
warning: missing documentation for a method
--> rust/kernel/num.rs:16:5
|
16 | fn lower_32_bits(self) -> u32;
| ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
warning: missing documentation for a function
--> rust/kernel/num.rs:33:1
|
33 | pub const fn upper_32_bits(v: u64) -> u32 {
| ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
warning: missing documentation for a function
--> rust/kernel/num.rs:37:1
|
37 | pub const fn lower_32_bits(v: u64) -> u32 {
| ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
warning: missing documentation for a function
--> rust/kernel/num.rs:41:1
|
41 | pub const fn u32s_to_u64(high: u32, low: u32) -> u64 {
| ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
warning: 5 warnings emitted
next prev parent reply other threads:[~2025-03-10 20:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-04 13:53 [RFC PATCH v2 0/5] gpu: nova-core: register definitions and basic timer and falcon devices Alexandre Courbot
2025-03-04 13:53 ` [PATCH RFC v2 1/5] rust: add useful ops for u64 Alexandre Courbot
2025-03-10 20:46 ` Timur Tabi [this message]
2025-03-04 13:53 ` [PATCH RFC v2 2/5] rust: make ETIMEDOUT error available Alexandre Courbot
2025-03-04 13:53 ` [PATCH RFC v2 3/5] gpu: nova-core: add register definition macro Alexandre Courbot
2025-03-04 13:54 ` [PATCH RFC v2 4/5] gpu: nova-core: add basic timer device Alexandre Courbot
2025-03-04 13:54 ` [PATCH RFC v2 5/5] gpu: nova-core: add falcon register definitions and probe code Alexandre Courbot
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=ab9b34381f6d5889e978bef352b923455b475ae6.camel@nvidia.com \
--to=ttabi@nvidia.com \
--cc=a.hindborg@kernel.org \
--cc=acourbot@nvidia.com \
--cc=airlied@gmail.com \
--cc=alex.gaynor@gmail.com \
--cc=aliceryhl@google.com \
--cc=benno.lossin@proton.me \
--cc=bjorn3_gh@protonmail.com \
--cc=boqun.feng@gmail.com \
--cc=bskeggs@nvidia.com \
--cc=dakr@kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=gary@garyguo.net \
--cc=jhubbard@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nouveau@lists.freedesktop.org \
--cc=ojeda@kernel.org \
--cc=rust-for-linux@vger.kernel.org \
--cc=simona@ffwll.ch \
--cc=tmgross@umich.edu \
/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).