All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michal Wajdeczko <michal.wajdeczko@intel.com>
To: "Dixit, Ashutosh" <ashutosh.dixit@intel.com>,
	Rodrigo Vivi <rodrigo.vivi@intel.com>
Cc: intel-xe@lists.freedesktop.org,
	Umesh Nerlige Ramappa <umesh.nerlige.ramappa@intel.com>
Subject: Re: [PATCH] drm/xe/oa: Fix 'enum drm_xe_perf_type' kernel doc warnings
Date: Sat, 22 Jun 2024 11:17:11 +0200	[thread overview]
Message-ID: <fa258ff8-86f2-4802-ba54-cd6705ce6e3d@intel.com> (raw)
In-Reply-To: <87wmmihtbw.wl-ashutosh.dixit@intel.com>



On 21.06.2024 23:36, Dixit, Ashutosh wrote:
> On Fri, 21 Jun 2024 12:45:43 -0700, Michal Wajdeczko wrote:
>>
> 
> Hi Michal,
> 
>>
>> On 21.06.2024 21:09, Ashutosh Dixit wrote:
>>> Include kernel doc's for 'enum drm_xe_perf_type' to fix kernel doc
>>> warnings.
>>>
>>> Reported-by: Michal Wajdeczko <michal.wajdeczko@intel.com>
>>> Signed-off-by: Ashutosh Dixit <ashutosh.dixit@intel.com>
>>> ---
>>>  include/uapi/drm/xe_drm.h | 5 ++++-
>>>  1 file changed, 4 insertions(+), 1 deletion(-)
>>>
>>> diff --git a/include/uapi/drm/xe_drm.h b/include/uapi/drm/xe_drm.h
>>> index 93e00be44b2d..d831f277f186 100644
>>> --- a/include/uapi/drm/xe_drm.h
>>> +++ b/include/uapi/drm/xe_drm.h
>>> @@ -1379,8 +1379,11 @@ struct drm_xe_wait_user_fence {
>>>   * enum drm_xe_perf_type - Perf stream types
>>>   */
>>>  enum drm_xe_perf_type {
>>> +	/** @DRM_XE_PERF_TYPE_OA: OA perf stream type */
>>> 	DRM_XE_PERF_TYPE_OA,
>>> -	__DRM_XE_PERF_TYPE_MAX, /* non-ABI */
>>> +
>>> +	/** @__DRM_XE_PERF_TYPE_MAX: Non-ABI */
>>
>> hmm, I would rather not document it at all, by marking it as:
>>
>> 	/* private: */
>>
>> see https://www.kernel.org/doc/html/next/doc-guide/kernel-doc.html#members
>>
>>> +	__DRM_XE_PERF_TYPE_MAX,
>>>  };
>>>
>>>  /**
> 
> Unfortunately, not documenting it doesn't seem to work and will result in
> kernel-doc error below:
> 
> $ ./scripts/kernel-doc -Werror -none include/uapi/drm/xe_drm.h
> include/uapi/drm/xe_drm.h:1388: warning: Enum value '__DRM_XE_PERF_TYPE_MAX' not described in enum 'drm_xe_perf_type'
> 1 warnings as Errors

hmm, but below diff works for me:

diff --git a/include/uapi/drm/xe_drm.h b/include/uapi/drm/xe_drm.h
index 93e00be44b2d..081e584240e6 100644
--- a/include/uapi/drm/xe_drm.h
+++ b/include/uapi/drm/xe_drm.h
@@ -1379,7 +1379,9 @@ struct drm_xe_wait_user_fence {
  * enum drm_xe_perf_type - Perf stream types
  */
 enum drm_xe_perf_type {
+       /** @DRM_XE_PERF_TYPE_OA: OA perf stream type */
        DRM_XE_PERF_TYPE_OA,
+       /* private: */
        __DRM_XE_PERF_TYPE_MAX, /* non-ABI */
 };


make sure you don't use /** private: */ as this might be not recognized

OTOH, if __DRM_XE_PERF_TYPE_MAX is not a real ABI definition, why did we
put this into uabi header?

see also DRM_XE_OA_PROPERTY_MAX that IMO should be either removed from
uabi or at least marked as a 'private'

+ Rodrigo

> 
> Thanks.
> --
> Ashutosh

  reply	other threads:[~2024-06-22  9:17 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-21 19:09 [PATCH] drm/xe/oa: Fix 'enum drm_xe_perf_type' kernel doc warnings Ashutosh Dixit
2024-06-21 19:14 ` ✓ CI.Patch_applied: success for " Patchwork
2024-06-21 19:14 ` ✗ CI.checkpatch: warning " Patchwork
2024-06-21 19:15 ` ✓ CI.KUnit: success " Patchwork
2024-06-21 19:27 ` ✓ CI.Build: " Patchwork
2024-06-21 19:29 ` ✓ CI.Hooks: " Patchwork
2024-06-21 19:31 ` ✓ CI.checksparse: " Patchwork
2024-06-21 19:45 ` [PATCH] " Michal Wajdeczko
2024-06-21 21:36   ` Dixit, Ashutosh
2024-06-22  9:17     ` Michal Wajdeczko [this message]
2024-06-22 16:03       ` Dixit, Ashutosh
2024-06-23 20:14         ` Dixit, Ashutosh
2024-06-21 19:54 ` ✓ CI.BAT: success for " Patchwork
2024-06-21 21:02 ` ✗ CI.FULL: failure " Patchwork

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=fa258ff8-86f2-4802-ba54-cd6705ce6e3d@intel.com \
    --to=michal.wajdeczko@intel.com \
    --cc=ashutosh.dixit@intel.com \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=rodrigo.vivi@intel.com \
    --cc=umesh.nerlige.ramappa@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.