From: Thomas Gleixner <tglx@linutronix.de>
To: Randy Dunlap <rdunlap@infradead.org>, linux-kernel@vger.kernel.org
Cc: Daniel Lezcano <daniel.lezcano@linaro.org>
Subject: Re: [PATCH] genirq/timings: add kernel-doc for a function param
Date: Wed, 15 Jan 2025 10:59:57 +0100 [thread overview]
Message-ID: <87a5bscs82.ffs@tglx> (raw)
In-Reply-To: <20250111062954.910657-1-rdunlap@infradead.org>
On Fri, Jan 10 2025 at 22:29, Randy Dunlap wrote:
> Add the description for @now to eliminate a kernel-doc warning.
> (Is this function used? I don't see it being called.)
That's indeed a good question.
Daniel, what's the state of this after 7+ years of being in "comes soon"
state?
Thanks,
tglx
next prev parent reply other threads:[~2025-01-15 9:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-11 6:29 [PATCH] genirq/timings: add kernel-doc for a function param Randy Dunlap
2025-01-15 9:59 ` Thomas Gleixner [this message]
2025-01-15 12:09 ` Daniel Lezcano
2025-01-15 16:06 ` Thomas Gleixner
2025-01-15 19:03 ` [tip: irq/core] genirq/timings: Add kernel-doc for a function parameter tip-bot2 for Randy Dunlap
2025-01-15 20:47 ` tip-bot2 for Randy Dunlap
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=87a5bscs82.ffs@tglx \
--to=tglx@linutronix.de \
--cc=daniel.lezcano@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@infradead.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;
as well as URLs for NNTP newsgroup(s).