From: Jani Nikula <jani.nikula@linux.intel.com>
To: Amogh Cheluvaraj <amogh.linux.kernel.dev@gmail.com>,
airlied@gmail.com, daniel@ffwll.ch,
maarten.lankhorst@linux.intel.com, mripard@kernel.org,
tzimmermann@suse.de, corbet@lwn.net,
javier.carrasco.cruz@gmail.com, skhan@linuxfoundation.org
Cc: Amogh Cheluvaraj <amogh.linux.kernel.dev@gmail.com>,
dri-devel@lists.freedesktop.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Fix duplicate C declaration warnings
Date: Thu, 21 Mar 2024 17:37:25 +0200 [thread overview]
Message-ID: <871q83mw96.fsf@intel.com> (raw)
In-Reply-To: <20240321115738.51188-1-amogh.linux.kernel.dev@gmail.com>
On Thu, 21 Mar 2024, Amogh Cheluvaraj <amogh.linux.kernel.dev@gmail.com> wrote:
> Fix the duplicate C declaration warnings found on
> Documentation/gpu/drm-kms.rst that was found by
> compiling htmldocs
Please paste the warnings here.
BR,
Jani.
>
> Signed-off-by: Amogh Cheluvaraj <amogh.linux.kernel.dev@gmail.com>
> ---
> Documentation/gpu/drm-kms.rst | 6 ------
> 1 file changed, 6 deletions(-)
>
> diff --git a/Documentation/gpu/drm-kms.rst b/Documentation/gpu/drm-kms.rst
> index 13d3627d8bc0..a4145f391e43 100644
> --- a/Documentation/gpu/drm-kms.rst
> +++ b/Documentation/gpu/drm-kms.rst
> @@ -357,9 +357,6 @@ Format Functions Reference
> .. kernel-doc:: include/drm/drm_fourcc.h
> :internal:
>
> -.. kernel-doc:: drivers/gpu/drm/drm_fourcc.c
> - :export:
> -
> .. _kms_dumb_buffer_objects:
>
> Dumb Buffer Objects
> @@ -458,9 +455,6 @@ KMS Locking
> .. kernel-doc:: include/drm/drm_modeset_lock.h
> :internal:
>
> -.. kernel-doc:: drivers/gpu/drm/drm_modeset_lock.c
> - :export:
> -
> KMS Properties
> ==============
--
Jani Nikula, Intel
next prev parent reply other threads:[~2024-03-21 15:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-21 11:57 [PATCH] Fix duplicate C declaration warnings Amogh Cheluvaraj
2024-03-21 15:37 ` Jani Nikula [this message]
2024-03-22 19:00 ` Amogh
-- strict thread matches above, loose matches on Subject: below --
2024-03-23 16:30 Amogh Cheluvaraj
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=871q83mw96.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=airlied@gmail.com \
--cc=amogh.linux.kernel.dev@gmail.com \
--cc=corbet@lwn.net \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=javier.carrasco.cruz@gmail.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--cc=skhan@linuxfoundation.org \
--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;
as well as URLs for NNTP newsgroup(s).