mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Andreas Hindborg <a.hindborg@kernel.org>,
	Danilo Krummrich <dakr@kernel.org>
Cc: Alexandre Courbot <acourbot@nvidia.com>,
	FUJITA Tomonori <fujita.tomonori@gmail.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: linux-next: manual merge of the rust-timekeeping tree with the drm-nova tree
Date: Tue, 24 Jun 2025 19:51:42 +1000	[thread overview]
Message-ID: <20250624195142.1050e147@canb.auug.org.au> (raw)

[-- Attachment #1: Type: text/plain, Size: 1046 bytes --]

Hi all,

After merging the rust-timekeeping tree, today's linux-next build
(x86_64 allmodconfig) failed like this:

error[E0599]: no method named `as_nanos` found for struct `Delta` in the current scope
  --> drivers/gpu/nova-core/util.rs:45:33
   |
45 |         if start_time.elapsed().as_nanos() > timeout.as_nanos() as i64 {
   |                                 ^^^^^^^^ method not found in `Delta`

error: aborting due to 1 previous error

For more information about this error, try `rustc --explain E0599`.

Caused by commits

  2ed94606a0fe ("rust: time: Rename Delta's methods from as_* to into_*")
  768dfbfc98e2 ("rust: time: Make Instant generic over ClockSource")

interacting with commit

  a03c9bd953c2 ("gpu: nova-core: add helper function to wait on condition")

from the drm-nova tree.

I tried to fix it up, but this lead down a rabbit hole and my rust
skills are poor, so I just dropped the rust-timekeeping tree for today.
A merge resolution would be appreciated.

-- 
Cheers,
Stephen Rothwell

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

             reply	other threads:[~2025-06-24  9:51 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <iuo4BpdTglZkpW9Xyy1ehjFspmj3ay0q7iejyeOShBG0HLZmIrhzIpi0eG_wBv71ZPPCgh2lcn2BOsrFHOegfg==@protonmail.internalid>
2025-06-24  9:51 ` Stephen Rothwell [this message]
2025-06-24 11:48   ` Andreas Hindborg
2025-06-24 12:03     ` Alexandre Courbot
2025-06-24 12:16       ` Danilo Krummrich
2025-06-24 19:02         ` Andreas Hindborg
2025-06-25  6:13           ` Stephen Rothwell
2025-06-26  7:05             ` Stephen Rothwell
2025-08-01  7:18   ` Stephen Rothwell

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=20250624195142.1050e147@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=a.hindborg@kernel.org \
    --cc=acourbot@nvidia.com \
    --cc=dakr@kernel.org \
    --cc=fujita.tomonori@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.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®