From: Randy Dunlap <rdunlap@infradead.org>
To: "Usyskin, Alexander" <alexander.usyskin@intel.com>,
"dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>
Cc: "Petr Vorel" <pvorel@suse.cz>,
"Gote, Nitin R" <nitin.r.gote@intel.com>,
"De Marchi, Lucas" <lucas.demarchi@intel.com>,
"Jani Nikula" <jani.nikula@linux.intel.com>,
"Vivi, Rodrigo" <rodrigo.vivi@intel.com>,
"Thomas Hellström" <thomas.hellstrom@linux.intel.com>,
"Joonas Lahtinen" <joonas.lahtinen@linux.intel.com>,
"Tvrtko Ursulin" <tursulin@ursulin.net>,
"intel-gfx@lists.freedesktop.org"
<intel-gfx@lists.freedesktop.org>,
"intel-xe@lists.freedesktop.org" <intel-xe@lists.freedesktop.org>,
"David Airlie" <airlied@gmail.com>,
"Simona Vetter" <simona@ffwll.ch>
Subject: Re: [PATCH v2] mei: intel_lb_mei_interface.h: mark struct member with kernel-doc
Date: Sun, 19 Oct 2025 17:38:06 -0700 [thread overview]
Message-ID: <f6e3c761-a676-4351-902c-5fbff9f8db6f@infradead.org> (raw)
In-Reply-To: <CY5PR11MB6366AC1589B2FE4E054ED6CCEDF4A@CY5PR11MB6366.namprd11.prod.outlook.com>
On 10/19/25 12:30 AM, Usyskin, Alexander wrote:
>> Subject: [PATCH v2] mei: intel_lb_mei_interface.h: mark struct member with
>> kernel-doc
>>
>> Use correct kernel-doc notation to prevent 3 kernel-doc warnings.
>> @push_payload is a struct member here, not a function, so use '@'
>> and ':' in its description.
>>
>> Warning: intel_lb_mei_interface.h:55 Incorrect use of kernel-doc format:
>> * push_payload - Sends a payload to the authentication firmware
>> Warning: intel_lb_mei_interface.h:67 Invalid param:
>> * @dev: Device struct corresponding to the mei device
>> * @type: Payload type (see &enum intel_lb_type)
>> * @flags: Payload flags bitmap (e.g. %INTEL_LB_FLAGS_IS_PERSISTENT)
>> * @payload: Pointer to payload buffer
>> * @payload_size: Payload buffer size in bytes
>> * * Return: 0 success, negative errno value on transport failure,
>> * positive status returned by firmware */
>> int (*push_payload)(struct device *dev, u32 type, u32 flags, const void
>> *payload, size_t payload_size)
>> Warning: intel_lb_mei_interface.h:67 struct member '* @dev: Device struct
>> corresponding to the mei device * @type: Payload type (see &enum
>> intel_lb_type' not described in 'intel_lb_component_ops'
>>
>
> Not sure about the right format here but this patch makes things better.
Yeah, we don't have a way to document callbacks in kernel-doc.
@push_payload is just a struct member here, not a function.
And the callback parameters aren't struct members. I just
didn't remove them since it's nice to have them documented
and this is the most logical/central place to do that
(most of this IMO).
> Acked-by: Alexander Usyskin <alexander.usyskin@intel.com>
>
>> Fixes: 741eeabb7c78 ("mei: late_bind: add late binding component driver")
>> Signed-off-by: Randy Dunlap <rdunlap@infradead.org>
>> Reviewed-by: Petr Vorel <pvorel@suse.cz>
>> Reviewed-by: Nitin Gote <nitin.r.gote@intel.com>
>> ---
>> v2: reformat long kernel-doc warning lines to <= 75 chars. (Nitin)
>>
>> Cc: Alexander Usyskin <alexander.usyskin@intel.com>
>> Cc: Lucas De Marchi <lucas.demarchi@intel.com>
>> Cc: Jani Nikula <jani.nikula@linux.intel.com>
>> Cc: Rodrigo Vivi <rodrigo.vivi@intel.com>
>> Cc: Thomas Hellström <thomas.hellstrom@linux.intel.com>
>> Cc: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
>> Cc: Tvrtko Ursulin <tursulin@ursulin.net>
>> Cc: intel-gfx@lists.freedesktop.org
>> Cc: intel-xe@lists.freedesktop.org
>> Cc: David Airlie <airlied@gmail.com>
>> Cc: Simona Vetter <simona@ffwll.ch>
>> Cc: dri-devel@lists.freedesktop.org
>> ---
>> include/drm/intel/intel_lb_mei_interface.h | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> --- linux-next-20251013.orig/include/drm/intel/intel_lb_mei_interface.h
>> +++ linux-next-20251013/include/drm/intel/intel_lb_mei_interface.h
>> @@ -53,7 +53,7 @@ enum intel_lb_status {
>> */
>> struct intel_lb_component_ops {
>> /**
>> - * push_payload - Sends a payload to the authentication firmware
>> + * @push_payload: Sends a payload to the authentication firmware
>> * @dev: Device struct corresponding to the mei device
>> * @type: Payload type (see &enum intel_lb_type)
>> * @flags: Payload flags bitmap (e.g.
>> %INTEL_LB_FLAGS_IS_PERSISTENT)
--
~Randy
prev parent reply other threads:[~2025-10-20 0:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-16 19:09 [PATCH v2] mei: intel_lb_mei_interface.h: mark struct member with kernel-doc Randy Dunlap
2025-10-16 23:27 ` ✗ i915.CI.BAT: failure for mei: intel_lb_mei_interface.h: mark struct member with kernel-doc (rev2) Patchwork
2025-10-19 7:30 ` [PATCH v2] mei: intel_lb_mei_interface.h: mark struct member with kernel-doc Usyskin, Alexander
2025-10-20 0:38 ` Randy Dunlap [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=f6e3c761-a676-4351-902c-5fbff9f8db6f@infradead.org \
--to=rdunlap@infradead.org \
--cc=airlied@gmail.com \
--cc=alexander.usyskin@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=jani.nikula@linux.intel.com \
--cc=joonas.lahtinen@linux.intel.com \
--cc=lucas.demarchi@intel.com \
--cc=nitin.r.gote@intel.com \
--cc=pvorel@suse.cz \
--cc=rodrigo.vivi@intel.com \
--cc=simona@ffwll.ch \
--cc=thomas.hellstrom@linux.intel.com \
--cc=tursulin@ursulin.net \
/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).