From: Tejun Heo <tj@kernel.org>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: linux-kernel@vger.kernel.org, David Vernet <void@manifault.com>,
Andrea Righi <arighi@nvidia.com>,
Changwoo Min <changwoo@igalia.com>,
Ingo Molnar <mingo@redhat.com>,
Peter Zijlstra <peterz@infradead.org>,
bpf@vger.kernel.org
Subject: Re: [PATCH] sched_ext: fix kernel-doc warnings
Date: Mon, 13 Jan 2025 08:24:36 -1000 [thread overview]
Message-ID: <Z4VaZB5VkwzCG_va@slm.duckdns.org> (raw)
In-Reply-To: <20250111063136.910862-1-rdunlap@infradead.org>
On Fri, Jan 10, 2025 at 10:31:36PM -0800, Randy Dunlap wrote:
> Use the correct function parameter names and function names.
> Use the correct kernel-doc comment format for struct sched_ext_ops
> to eliminate a bunch of warnings.
Applied to sched_ext/for-6.14.
Thanks.
--
tejun
prev parent reply other threads:[~2025-01-13 18:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-11 6:31 [PATCH] sched_ext: fix kernel-doc warnings Randy Dunlap
2025-01-11 9:45 ` Andrea Righi
2025-01-11 17:27 ` Randy Dunlap
2025-01-11 17:30 ` Andrea Righi
2025-01-13 18:24 ` Tejun Heo [this message]
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=Z4VaZB5VkwzCG_va@slm.duckdns.org \
--to=tj@kernel.org \
--cc=arighi@nvidia.com \
--cc=bpf@vger.kernel.org \
--cc=changwoo@igalia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=rdunlap@infradead.org \
--cc=void@manifault.com \
/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