Re: [PATCH v9 01/13] rust: hrtimer: introduce hrtimer support

[Miguel Ojeda]

On Mon, Feb 24, 2025 at 5:31 PM Boqun Feng <boqun.feng@xxxxxxxxx> wrote:
>
> On Mon, Feb 24, 2025 at 05:23:59PM +0100, Miguel Ojeda wrote:
> >
> > side -- Andreas and I discussed it the other day. The description of
> > the issue has some lines, but perhaps the commit message could
>
> Do you have a link to the issue?

Sorry, I meant "description of the symbol", i.e. the description field
in the patch.

> I asked because hrtimer API is always available regardless of the
> configuration, and it's such a core API, so it should always be there
> (Rust or C).

It may not make sense for something that is always built on the C
side, yeah. I think the intention here may be that one can easily
disable it while "developing" a change on the C side. I am not sure
what "developing" means here, though, and we need to be careful --
after all, Kconfig options are visible to users and they do not care
about that.

If it is just for local development, then I would expect the
maintainers to simply disable Rust entirely. I guess that may be
harder in the medium/long-term future, but currently, I don't see a
big issue not enabling Rust while developing the C side, no?

Cheers,
Miguel