Re: [GIT PULL] Rust timekeeping for v6.18

[Andreas Hindborg <a.hindborg@kernel.org>]

"Miguel Ojeda" <miguel.ojeda.sandonis@gmail.com> writes:

> On Fri, Sep 19, 2025 at 1:46 PM Andreas Hindborg <a.hindborg@kernel.org> wrote:
>>
>>  - Additional functionality for `HrTimer` that allows use of operations
>>    that can only be executed in timer callback context, or with
>>    exclusive access to a timer that is not armed.
>
> Should I use this one or the bullet from the tag itself?

I would suggest you use the info in the tag.

> (For future PRs, please avoid duplicating the summary, i.e. the part
> that goes outside the tag message should generally be about meta
> comments that should not go into the repository, like the linux-next
> note.)

I am actually a bit confused as to what information you prefer in the
tag and what you prefer in the pull request message itself. I would
appreciate a reminder to use as a guideline. They seem redundant to me,
which is why I used an empty tag last cycle.

>
> By the way, I noticed a commit without a commit message apart from the
> title and tags -- for future PRs, please try to always ensure there is
> some context, especially explaining why something is added:
>
>     ac0a7bd27f65 ("rust: hrtimer: Add forward_now() to HrTimer and
> HrTimerCallbackContext")

Thanks, I missed that somehow. Usually `check_patch.pl` will complain
for this kind of thing.


Best regards,
Andreas Hindborg