linux-kernel - Re: linux-next: manual merge of the rust-timekeeping tree with the drm-nova tree

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <aFqXKKAxQp0yxUvL@pollux>
Date: Tue, 24 Jun 2025 14:16:40 +0200
From: Danilo Krummrich <dakr@...nel.org>
To: Alexandre Courbot <acourbot@...dia.com>
Cc: Andreas Hindborg <a.hindborg@...nel.org>,
	Stephen Rothwell <sfr@...b.auug.org.au>,
	FUJITA Tomonori <fujita.tomonori@...il.com>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Linux Next Mailing List <linux-next@...r.kernel.org>
Subject: Re: linux-next: manual merge of the rust-timekeeping tree with the
 drm-nova tree

On Tue, Jun 24, 2025 at 09:03:48PM +0900, Alexandre Courbot wrote:
> On Tue Jun 24, 2025 at 8:48 PM JST, Andreas Hindborg wrote:
> > For the Nova people: You might consider if it makes sense to take a
> > `kernel::time::Delta<C>` for the timeout.
> 
> It probably does now that it is available. I'm willing to do it this
> cycle if we can find a way to not break the build. Should we have a tag
> to merge into nova-next or something?

I'm not sure about the generic in Delta mentioned by Andreas above, but the
Detla type did land in the last merge window, so it's available in the nova
tree already.

In case it would not have been, I wouldn't recommend doing signed tags for such
a minor thing. We should only do that when things are really getting into the
way.

- Danilo