All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rajat Jain <rajatja@google.com>
To: Hans de Goede <hdegoede@redhat.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
	dri-devel@lists.freedesktop.org,
	Thomas Zimmermann <tzimmermann@suse.de>
Subject: Re: [PATCH] drm/privacy-screen: Fix sphinx warning
Date: Mon, 7 Feb 2022 10:06:50 -0800	[thread overview]
Message-ID: <CACK8Z6HnOU9W6BUnBeN2c3oFKvxaTaXdOXSR7hsNR8EAxdyaTw@mail.gmail.com> (raw)
In-Reply-To: <20220207113307.346281-1-hdegoede@redhat.com>

In case it matters...

On Mon, Feb 7, 2022 at 3:33 AM Hans de Goede <hdegoede@redhat.com> wrote:
>
> Fix the following warning from "make htmldocs":
>
> drivers/gpu/drm/drm_privacy_screen.c:392:
>   warning: Function parameter or member 'data' not described in
>   'drm_privacy_screen_register'
>
> Fixes: 30598d925d46 ("drm/privacy_screen: Add drvdata in drm_privacy_screen")
> Cc: Rajat Jain <rajatja@google.com>
> Reported-by: Stephen Rothwell <sfr@canb.auug.org.au>
> Signed-off-by: Hans de Goede <hdegoede@redhat.com>

Acked-by: Rajat Jain <rajatja@google.com>

Thanks Hans for taking care of this for me.

Best Regards,

Rajat


> ---
>  drivers/gpu/drm/drm_privacy_screen.c | 1 +
>  1 file changed, 1 insertion(+)
>
> diff --git a/drivers/gpu/drm/drm_privacy_screen.c b/drivers/gpu/drm/drm_privacy_screen.c
> index 03b149cc455b..45c080134488 100644
> --- a/drivers/gpu/drm/drm_privacy_screen.c
> +++ b/drivers/gpu/drm/drm_privacy_screen.c
> @@ -379,6 +379,7 @@ static void drm_privacy_screen_device_release(struct device *dev)
>   * drm_privacy_screen_register - register a privacy-screen
>   * @parent: parent-device for the privacy-screen
>   * @ops: &struct drm_privacy_screen_ops pointer with ops for the privacy-screen
> + * @data: Private data owned by the privacy screen provider
>   *
>   * Create and register a privacy-screen.
>   *
> --
> 2.33.1
>

  parent reply	other threads:[~2022-02-07 18:07 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-07 11:33 [PATCH] drm/privacy-screen: Fix sphinx warning Hans de Goede
2022-02-07 11:37 ` Simon Ser
2022-02-07 11:40   ` Hans de Goede
2022-02-07 18:06 ` Rajat Jain [this message]
  -- strict thread matches above, loose matches on Subject: below --
2022-01-26 15:11 Hans de Goede
2022-02-07 11:43 ` Simon Ser
2022-02-07 12:55   ` Hans de Goede
2022-02-07 12:57     ` Simon Ser

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=CACK8Z6HnOU9W6BUnBeN2c3oFKvxaTaXdOXSR7hsNR8EAxdyaTw@mail.gmail.com \
    --to=rajatja@google.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=hdegoede@redhat.com \
    --cc=sfr@canb.auug.org.au \
    --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 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.