From: Danilo Krummrich <dakr@kernel.org>
To: Alexandre Courbot <acourbot@nvidia.com>
Cc: Andreas Hindborg <a.hindborg@kernel.org>,
Stephen Rothwell <sfr@canb.auug.org.au>,
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: Re: linux-next: manual merge of the rust-timekeeping tree with the drm-nova tree
Date: Tue, 24 Jun 2025 14:16:40 +0200 [thread overview]
Message-ID: <aFqXKKAxQp0yxUvL@pollux> (raw)
In-Reply-To: <DAUQZ1TY9VT3.UJEFQ96157DJ@nvidia.com>
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
next prev parent reply other threads:[~2025-06-24 12:16 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 ` linux-next: manual merge of the rust-timekeeping tree with the drm-nova tree Stephen Rothwell
2025-06-24 11:48 ` Andreas Hindborg
2025-06-24 12:03 ` Alexandre Courbot
2025-06-24 12:16 ` Danilo Krummrich [this message]
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=aFqXKKAxQp0yxUvL@pollux \
--to=dakr@kernel.org \
--cc=a.hindborg@kernel.org \
--cc=acourbot@nvidia.com \
--cc=fujita.tomonori@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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;
as well as URLs for NNTP newsgroup(s).