Linux Tegra architecture development
 help / color / mirror / Atom feed
From: Mikko Perttunen <mperttunen@nvidia.com>
To: dri-devel@lists.freedesktop.org, Randy Dunlap <rdunlap@infradead.org>
Cc: Randy Dunlap <rdunlap@infradead.org>,
	Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
	Maxime Ripard <mripard@kernel.org>,
	Thomas Zimmermann <tzimmermann@suse.de>,
	Thierry Reding <thierry.reding@gmail.com>,
	linux-tegra@vger.kernel.org,
	Jonathan Hunter <jonathanh@nvidia.com>,
	David Airlie <airlied@gmail.com>, Simona Vetter <simona@ffwll.ch>
Subject: Re: [PATCH RESEND] drm/tegra: dp: fix kernel-doc warnings in dp.h
Date: Tue, 03 Mar 2026 13:41:17 +0900	[thread overview]
Message-ID: <4932648.mvXUDI8C0e@senjougahara> (raw)
In-Reply-To: <20260219215535.469520-1-rdunlap@infradead.org>

On Friday, February 20, 2026 6:55 AM Randy Dunlap wrote:
> Use correct kernel-doc format and add missing nested struct entries to
> eliminate kernel-doc warnings:
> 
> Warning: drivers/gpu/drm/tegra/dp.h:28 Incorrect use of kernel-doc
> format: * tps3_supported:
> Warning: drivers/gpu/drm/tegra/dp.h:54 struct member 'tps3_supported'
>  not described in 'drm_dp_link_caps'
> dp.h:73: warning: Function parameter or struct member 'apply_training'
> not described in 'drm_dp_link_ops'
> dp.h:73: warning: Function parameter or struct member 'configure'
>  not described in 'drm_dp_link_ops'
> dp.h:160: warning: Excess struct member 'cr' description in
> 'drm_dp_link'
> 
> Signed-off-by: Randy Dunlap <rdunlap@infradead.org>
> ---
> Cc: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
> Cc: Maxime Ripard <mripard@kernel.org>
> Cc: Thomas Zimmermann <tzimmermann@suse.de>
> Cc: Thierry Reding <thierry.reding@gmail.com>
> Cc: Mikko Perttunen <mperttunen@nvidia.com>
> Cc: linux-tegra@vger.kernel.org
> Cc: Jonathan Hunter <jonathanh@nvidia.com>
> Cc: David Airlie <airlied@gmail.com>
> Cc: Simona Vetter <simona@ffwll.ch>
> ---
>  drivers/gpu/drm/tegra/dp.h |   12 +++++-------
>  1 file changed, 5 insertions(+), 7 deletions(-)
> 
> --- linux-next-20260218.orig/drivers/gpu/drm/tegra/dp.h
> +++ linux-next-20260218/drivers/gpu/drm/tegra/dp.h
> @@ -26,7 +26,7 @@ struct drm_dp_link_caps {
>  	bool enhanced_framing;
> 
>  	/**
> -	 * tps3_supported:
> +	 * @tps3_supported:
>  	 *
>  	 * training pattern sequence 3 supported for equalization
>  	 */
> @@ -62,12 +62,12 @@ void drm_dp_link_caps_copy(struct drm_dp
>   */
>  struct drm_dp_link_ops {
>  	/**
> -	 * @apply_training:
> +	 * @apply_training: apply the link training
>  	 */
>  	int (*apply_training)(struct drm_dp_link *link);
> 
>  	/**
> -	 * @configure:
> +	 * @configure: configure the DP link
>  	 */
>  	int (*configure)(struct drm_dp_link *link);
>  };
> @@ -113,6 +113,8 @@ struct drm_dp_link_train {
>   * @max_lanes: maximum number of lanes supported on the link
>   * @caps: capabilities supported on the link (see &drm_dp_link_caps)
>   * @aux_rd_interval: AUX read interval to use for training (in
> microseconds) + * @aux_rd_interval.cr: clock recovery read interval
> + * @aux_rd_interval.ce: channel equalization read interval
>   * @edp: eDP revision (0x11: eDP 1.1, 0x12: eDP 1.2, ...)
>   * @rate: currently configured link rate
>   * @lanes: currently configured number of lanes
> @@ -126,10 +128,6 @@ struct drm_dp_link {
> 
>  	struct drm_dp_link_caps caps;
> 
> -	/**
> -	 * @cr: clock recovery read interval
> -	 * @ce: channel equalization read interval
> -	 */
>  	struct {
>  		unsigned int cr;
>  		unsigned int ce;

Acked-by: Mikko Perttunen <mperttunen@nvidia.com>





      reply	other threads:[~2026-03-03  4:41 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-19 21:55 [PATCH RESEND] drm/tegra: dp: fix kernel-doc warnings in dp.h Randy Dunlap
2026-03-03  4:41 ` Mikko Perttunen [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=4932648.mvXUDI8C0e@senjougahara \
    --to=mperttunen@nvidia.com \
    --cc=airlied@gmail.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=jonathanh@nvidia.com \
    --cc=linux-tegra@vger.kernel.org \
    --cc=maarten.lankhorst@linux.intel.com \
    --cc=mripard@kernel.org \
    --cc=rdunlap@infradead.org \
    --cc=simona@ffwll.ch \
    --cc=thierry.reding@gmail.com \
    --cc=tzimmermann@suse.de \
    /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