From: "Danilo Krummrich" <dakr@kernel.org>
To: "Andreas Hindborg" <a.hindborg@kernel.org>
Cc: "FUJITA Tomonori" <fujita.tomonori@gmail.com>,
"Gary Guo" <gary@garyguo.net>,
"Alice Ryhl" <aliceryhl@google.com>,
"Daniel Almeida" <daniel.almeida@collabora.com>,
"Alexandre Courbot" <acourbot@nvidia.com>,
"Dave Airlie" <airlied@redhat.com>, <nova-gpu@lists.linux.dev>,
<dri-devel@lists.freedesktop.org>
Subject: Re: [PATCH v7 1/2] rust: time: expose as_nanos for clock sources.
Date: Thu, 12 Nov 2026 15:22:15 +0100 [thread overview]
Message-ID: <DMTASPUDKG3F.1H8JUZ5C0A2M3@kernel.org> (raw)
In-Reply-To: <87tslmupje.fsf@t14s.mail-host-address-is-not-set>
On Thu Nov 12, 2026 at 2:50 PM CET, Andreas Hindborg wrote:
> "Danilo Krummrich" <dakr@kernel.org> writes:
>
>> On Thu Nov 12, 2026 at 1:47 PM CET, Andreas Hindborg wrote:
>>>
>>> On Wed, 11 Nov 2026 15:23:24 +1000, Dave Airlie wrote:
>>>> 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 is needed for following nova patch.
>>>
>>> Applied, thanks!
>>
>> Do you mind if we take this through the DRM tree? Otherwise the subsequent patch
>> in this series has to wait for a cycle.
>
> No it is fine, I can drop it from my tree. I asked on v6 what you
> wanted, either way is fine :)
Great, thanks!
next prev parent reply other threads:[~2026-11-12 14:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-11 5:23 [PATCH v7 0/2] nova-core: add initial support for gpu timer (v7) Dave Airlie via B4 Relay
2026-11-11 5:23 ` [PATCH v7 1/2] rust: time: expose as_nanos for clock sources Dave Airlie via B4 Relay
2026-11-12 12:47 ` Andreas Hindborg
2026-11-12 12:59 ` Danilo Krummrich
2026-11-12 13:50 ` Andreas Hindborg
2026-11-12 14:22 ` Danilo Krummrich [this message]
2026-11-11 5:23 ` [PATCH v7 2/2] gpu: nova-core: add support for GPU timer block. (v7) Dave Airlie via B4 Relay
2026-11-12 13:28 ` 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=DMTASPUDKG3F.1H8JUZ5C0A2M3@kernel.org \
--to=dakr@kernel.org \
--cc=a.hindborg@kernel.org \
--cc=acourbot@nvidia.com \
--cc=airlied@redhat.com \
--cc=aliceryhl@google.com \
--cc=daniel.almeida@collabora.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox