From: "Alexandre Courbot" <acourbot@nvidia.com>
To: "Dave Airlie via B4 Relay" <devnull+airlied.redhat.com@kernel.org>
Cc: <airlied@redhat.com>, "Andreas Hindborg" <a.hindborg@kernel.org>,
"FUJITA Tomonori" <fujita.tomonori@gmail.com>,
"Gary Guo" <gary@garyguo.net>,
"Alice Ryhl" <aliceryhl@google.com>,
"Danilo Krummrich" <dakr@kernel.org>,
"Daniel Almeida" <daniel.almeida@collabora.com>,
<nova-gpu@lists.linux.dev>, <dri-devel@lists.freedesktop.org>
Subject: Re: [PATCH v4 1/2] rust: time: expose as_nanos for clock sources.
Date: Thu, 05 Nov 2026 23:21:54 +0900 [thread overview]
Message-ID: <DMNCEMXOXMWU.33914P6SZI2PL@nvidia.com> (raw)
In-Reply-To: <20261105-nova-timer-v4-1-45a7c121d4de@redhat.com>
On Thu Nov 5, 2026 at 12:07 PM JST, Dave Airlie via B4 Relay wrote:
> From: Dave Airlie <airlied@redhat.com>
>
> The nouveau C driver does ktime_to_ns(ktime_get()) to program
> the cpu ns into some hw/fw, so allow this method for rust drivers.
This sounds a bit like we are making this public for Nouveau. Maybe just
say it is needed for the next patch?
Regardless,
Reviewed-by: Alexandre Courbot <acourbot@nvidia.com>
next prev parent reply other threads:[~2026-11-05 14:22 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-05 3:07 [PATCH v4 0/2] nova-core: add initial support for gpu timer (v4) Dave Airlie
2026-11-05 3:07 ` Dave Airlie via B4 Relay
2026-11-05 3:07 ` [PATCH v4 1/2] rust: time: expose as_nanos for clock sources Dave Airlie
2026-11-05 3:07 ` Dave Airlie via B4 Relay
2026-11-05 14:21 ` Alexandre Courbot [this message]
2026-11-05 3:07 ` [PATCH v4 2/2] gpu: nova-core: add support for GPU timer block. (v4) Dave Airlie
2026-11-05 3:07 ` Dave Airlie via B4 Relay
2026-11-05 3:21 ` sashiko-bot
2026-11-05 14:43 ` Alexandre Courbot
2026-11-06 5:31 ` David Airlie
2026-11-06 14:41 ` 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=DMNCEMXOXMWU.33914P6SZI2PL@nvidia.com \
--to=acourbot@nvidia.com \
--cc=a.hindborg@kernel.org \
--cc=airlied@redhat.com \
--cc=aliceryhl@google.com \
--cc=dakr@kernel.org \
--cc=daniel.almeida@collabora.com \
--cc=devnull+airlied.redhat.com@kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=fujita.tomonori@gmail.com \
--cc=gary@garyguo.net \
--cc=nova-gpu@lists.linux.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.