public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@linux.intel.com>
To: R Sundar <prosunofficial@gmail.com>,
	Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
	Maxime Ripard <mripard@kernel.org>,
	Thomas Zimmermann <tzimmermann@suse.de>,
	David Airlie <airlied@gmail.com>, Simona Vetter <simona@ffwll.ch>
Cc: dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org,
	R Sundar <prosunofficial@gmail.com>
Subject: Re: [PATCH linux-next] drm: Fix for kernel doc warning
Date: Wed, 09 Oct 2024 18:58:06 +0300	[thread overview]
Message-ID: <87frp58e0h.fsf@intel.com> (raw)
In-Reply-To: <20241003023806.17537-1-prosunofficial@gmail.com>

On Thu, 03 Oct 2024, R Sundar <prosunofficial@gmail.com> wrote:
> Added colon in kernel-doc comment to fix the warning.
>
> ./include/drm/drm_drv.h:372: warning: Incorrect use of kernel-doc format:          * @fbdev_probe
> ./include/drm/drm_drv.h:435: warning: Function parameter or struct member 'fbdev_probe' not described in 'drm_driver'
>
> Signed-off-by: R Sundar <prosunofficial@gmail.com>

Pushed to drm-misc-next, thanks for the patch.

BR,
Jani.

> ---
>  include/drm/drm_drv.h | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/include/drm/drm_drv.h b/include/drm/drm_drv.h
> index 36a606af4ba1..1bbbcb8e2d23 100644
> --- a/include/drm/drm_drv.h
> +++ b/include/drm/drm_drv.h
> @@ -369,7 +369,7 @@ struct drm_driver {
>  			       uint64_t *offset);
>  
>  	/**
> -	 * @fbdev_probe
> +	 * @fbdev_probe:
>  	 *
>  	 * Allocates and initialize the fb_info structure for fbdev emulation.
>  	 * Furthermore it also needs to allocate the DRM framebuffer used to

-- 
Jani Nikula, Intel

      reply	other threads:[~2024-10-09 15:58 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-03  2:38 [PATCH linux-next] drm: Fix for kernel doc warning R Sundar
2024-10-09 15:58 ` Jani Nikula [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=87frp58e0h.fsf@intel.com \
    --to=jani.nikula@linux.intel.com \
    --cc=airlied@gmail.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=maarten.lankhorst@linux.intel.com \
    --cc=mripard@kernel.org \
    --cc=prosunofficial@gmail.com \
    --cc=simona@ffwll.ch \
    --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