Rust for Linux List
 help / color / mirror / Atom feed
From: "Alexandre Courbot" <acourbot@nvidia.com>
To: "FUJITA Tomonori" <tomo@flapping.org>
Cc: <a.hindborg@kernel.org>, <ojeda@kernel.org>,
	<aliceryhl@google.com>, <anna-maria@linutronix.de>,
	<bjorn3_gh@protonmail.com>, <boqun@kernel.org>, <dakr@kernel.org>,
	<daniel.almeida@collabora.com>, <frederic@kernel.org>,
	<gary@garyguo.net>, <jstultz@google.com>, <lossin@kernel.org>,
	<lyude@redhat.com>, <sboyd@kernel.org>, <tamird@kernel.org>,
	<tglx@kernel.org>, <tmgross@umich.edu>, <work@onurozkan.dev>,
	<rust-for-linux@vger.kernel.org>,
	"FUJITA Tomonori" <fujita.tomonori@gmail.com>
Subject: Re: [PATCH v1] rust: time: remove leftover "clock source" wording from doc comments
Date: Fri, 30 Oct 2026 14:22:26 +0900	[thread overview]
Message-ID: <DMHX6B824HCE.118N55GSMR1VQ@nvidia.com> (raw)
In-Reply-To: <20261030044803.3863267-1-tomo@flapping.org>

On Fri Oct 30, 2026 at 1:48 PM JST, FUJITA Tomonori wrote:
> From: FUJITA Tomonori <fujita.tomonori@gmail.com>
>
> Commit 6a8e2c63f2fe ("rust: time: rename ClockSource trait to ClockId")
> renamed the trait because it represents a `clockid_t`, not the C
> `struct clocksource`. Two doc comments still say "clock source".
>
> Replace them with "clock". This matches the `ClockId` doc ("Get the
> current time from the clock") and the C hrtimer_setup() kerneldoc
> ("@clock_id: the clock to be used").
>
> No functional change.
>
> Signed-off-by: FUJITA Tomonori <fujita.tomonori@gmail.com>

FWIW,

Reviewed-by: Alexandre Courbot <acourbot@nvidia.com>

  reply	other threads:[~2026-10-30  5:22 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <70lCMDfO9RKOmQM0cJWbGH-Xb2obLme9j31nmGPFgVtxFjpGGolzh6OVOtVaPwvM8dMHEIJSl8UOb9vq3abM_w==@protonmail.internalid>
2026-10-30  4:48 ` [PATCH v1] rust: time: remove leftover "clock source" wording from doc comments FUJITA Tomonori
2026-10-30  5:22   ` Alexandre Courbot [this message]
2026-10-30 12:41   ` Andreas Hindborg

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=DMHX6B824HCE.118N55GSMR1VQ@nvidia.com \
    --to=acourbot@nvidia.com \
    --cc=a.hindborg@kernel.org \
    --cc=aliceryhl@google.com \
    --cc=anna-maria@linutronix.de \
    --cc=bjorn3_gh@protonmail.com \
    --cc=boqun@kernel.org \
    --cc=dakr@kernel.org \
    --cc=daniel.almeida@collabora.com \
    --cc=frederic@kernel.org \
    --cc=fujita.tomonori@gmail.com \
    --cc=gary@garyguo.net \
    --cc=jstultz@google.com \
    --cc=lossin@kernel.org \
    --cc=lyude@redhat.com \
    --cc=ojeda@kernel.org \
    --cc=rust-for-linux@vger.kernel.org \
    --cc=sboyd@kernel.org \
    --cc=tamird@kernel.org \
    --cc=tglx@kernel.org \
    --cc=tmgross@umich.edu \
    --cc=tomo@flapping.org \
    --cc=work@onurozkan.dev \
    /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