From: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
"David E. Box" <david.e.box@linux.intel.com>,
Hans de Goede <hansg@kernel.org>,
platform-driver-x86@vger.kernel.org
Subject: Re: [PATCH] platform/x86/intel/vsec: correct kernel-doc comments
Date: Mon, 15 Dec 2025 16:10:37 +0200 (EET) [thread overview]
Message-ID: <cac479ad-e258-fb20-8005-3155e4a7f901@linux.intel.com> (raw)
In-Reply-To: <20251214201959.2195863-1-rdunlap@infradead.org>
[-- Attachment #1: Type: text/plain, Size: 2417 bytes --]
On Sun, 14 Dec 2025, Randy Dunlap wrote:
> Fix kernel-doc warnings in intel_vsec.h to eliminate all kernel-doc
> warnings:
>
> Warning: include/linux/intel_vsec.h:92 struct member 'read_telem' not
> described in 'pmt_callbacks'
> Warning: include/linux/intel_vsec.h:146 expecting prototype for struct
> intel_sec_device. Prototype was for struct intel_vsec_device instead
> Warning: include/linux/intel_vsec.h:146 struct member 'priv_data_size'
> not described in 'intel_vsec_device'
>
> Signed-off-by: Randy Dunlap <rdunlap@infradead.org>
> ---
> Cc: David E. Box <david.e.box@linux.intel.com>
> Cc: Hans de Goede <hansg@kernel.org>
> Cc: Ilpo Järvinen <ilpo.jarvinen@linux.intel.com>
> Cc: platform-driver-x86@vger.kernel.org
> ---
> include/linux/intel_vsec.h | 7 ++++---
> 1 file changed, 4 insertions(+), 3 deletions(-)
>
> --- linux-next-20251201.orig/include/linux/intel_vsec.h
> +++ linux-next-20251201/include/linux/intel_vsec.h
> @@ -80,8 +80,8 @@ enum intel_vsec_quirks {
>
> /**
> * struct pmt_callbacks - Callback infrastructure for PMT devices
> - * ->read_telem() when specified, called by client driver to access PMT data (instead
> - * of direct copy).
> + * @read_telem: when specified, called by client driver to access PMT
> + * data (instead of direct copy).
> * @pdev: PCI device reference for the callback's use
> * @guid: ID of data to acccss
> * @data: buffer for the data to be copied
Is it correct for kerneldoc to have the rest as @pdev, @guid, etc.,
they are parameters to the callback, not members of this struct?
> @@ -120,7 +120,7 @@ struct intel_vsec_platform_info {
> };
>
> /**
> - * struct intel_sec_device - Auxbus specific device information
> + * struct intel_vsec_device - Auxbus specific device information
> * @auxdev: auxbus device struct for auxbus access
> * @pcidev: pci device associated with the device
> * @resource: any resources shared by the parent
> @@ -128,6 +128,7 @@ struct intel_vsec_platform_info {
> * @num_resources: number of resources
> * @id: xarray id
> * @priv_data: any private data needed
> + * @priv_data_size: size of private data area
> * @quirks: specified quirks
> * @base_addr: base address of entries (if specified)
> * @cap_id: the enumerated id of the vsec feature
>
--
i.
next prev parent reply other threads:[~2025-12-15 14:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-14 20:19 Randy Dunlap
2025-12-15 14:10 ` Ilpo Järvinen [this message]
2025-12-15 18:47 ` Randy Dunlap
2025-12-15 19:21 ` Ilpo Järvinen
2025-12-15 19:59 ` Randy Dunlap
2025-12-15 20:24 ` Ilpo Järvinen
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=cac479ad-e258-fb20-8005-3155e4a7f901@linux.intel.com \
--to=ilpo.jarvinen@linux.intel.com \
--cc=david.e.box@linux.intel.com \
--cc=hansg@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=platform-driver-x86@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
all inboxes | Powered by JetHome®