From: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
To: linux-kernel@vger.kernel.org, Randy Dunlap <rdunlap@infradead.org>
Cc: Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>,
Hans de Goede <hansg@kernel.org>,
platform-driver-x86@vger.kernel.org
Subject: Re: [PATCH] platform/x86: intel-uncore-freq: fix all header kernel-doc warnings
Date: Tue, 18 Nov 2025 10:11:31 +0200 [thread overview]
Message-ID: <176345349126.8636.18069708901921659797.b4-ty@linux.intel.com> (raw)
In-Reply-To: <20251111060938.1998542-1-rdunlap@infradead.org>
On Mon, 10 Nov 2025 22:09:34 -0800, Randy Dunlap wrote:
> In file uncore-frequency/uncore-frequency-common.h,
> correct all kernel-doc warnings by adding missing leading " *" to some
> lines, adding a missing kernel-doc entry, and fixing a name typo.
>
> Warning: uncore-frequency-common.h:50 bad line:
> Storage for kobject attribute elc_low_threshold_percent
> Warning: uncore-frequency-common.h:52 bad line:
> Storage for kobject attribute elc_high_threshold_percent
> Warning: uncore-frequency-common.h:54 bad line:
> Storage for kobject attribute elc_high_threshold_enable
> Warning: uncore-frequency-common.h:92 struct member
> 'min_freq_khz_kobj_attr' not described in 'uncore_data'
> Warning: uncore-frequency-common.h:92 struct member
> 'die_id_kobj_attr' not described in 'uncore_data'
>
> [...]
Thank you for your contribution, it has been applied to my local
review-ilpo-fixes branch. Note it will show up in the public
platform-drivers-x86/review-ilpo-fixes branch only once I've pushed my
local branch there, which might take a while.
The list of commits applied:
[1/1] platform/x86: intel-uncore-freq: fix all header kernel-doc warnings
commit: db30233361f94e1a84450c607989bdb671100fb6
--
i.
prev parent reply other threads:[~2025-11-18 8:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-11 6:09 [PATCH] platform/x86: intel-uncore-freq: fix all header kernel-doc warnings Randy Dunlap
2025-11-18 8:11 ` Ilpo Järvinen [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=176345349126.8636.18069708901921659797.b4-ty@linux.intel.com \
--to=ilpo.jarvinen@linux.intel.com \
--cc=hansg@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=platform-driver-x86@vger.kernel.org \
--cc=rdunlap@infradead.org \
--cc=srinivas.pandruvada@linux.intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.