From: Greg KH <gregkh@linuxfoundation.org>
To: kushagra765@outlook.com
Cc: linux-doc@vger.kernel.org, corbet@lwn.net,
maarten.lankhorst@linux.intel.com, mripard@kernel.org,
tzimmermann@suse.de, airlied@linux.ie, daniel@ffwll.ch,
balbi@kernel.org, dhowells@redhat.com, arnd@arndb.de,
mcgrof@kernel.org, akpm@linux-foundation.org,
viro@zeniv.linux.org.uk, dri-devel@lists.freedesktop.org,
linux-kernel@vger.kernel.org, linux-usb@vger.kernel.org,
linux-cachefs@redhat.com
Subject: Re: [ PATCH ] Documentation: fixed doc-build warnings
Date: Sun, 27 Mar 2022 09:11:06 +0200 [thread overview]
Message-ID: <YkAOCrbbrMaYkiSb@kroah.com> (raw)
In-Reply-To: <TYZPR01MB3935D1963BFD458E85412E4DF81B9@TYZPR01MB3935.apcprd01.prod.exchangelabs.com>
On Sat, Mar 26, 2022 at 05:22:55PM +0530, kushagra765@outlook.com wrote:
> >From 9a9918b051d5709b5e14ca8afa29f3ef644b8688 Mon Sep 17 00:00:00 2001
> From: Kushagra Verma <kushagra765@outlook.com>
> Date: Sat, 26 Mar 2022 16:43:15 +0530
> Subject: [PATCH] Documentation: fixed doc-build warnings
This should not be in the body of the email, please fix :(
>
> This patch fixes the following (and 2 other) doc-build warnings:
> 1. ./include/linux/dcache.h:308: warning: expecting prototype for dget, dget_dlock(). Prototype was for dget_dlock() instead
>
> 2. ./include/linux/fscache.h:268: warning: Excess function parameter 'object' description in 'fscache_use_cookie'
>
> 3 ./include/linux/fscache.h:285: warning: Excess function parameter 'object' description in 'fscache_unuse_cookie'
>
> 4. ./drivers/gpu/drm/drm_format_helper.c:640: warning: Excess function parameter 'src' description in 'drm_fb_xrgb8888_to_mono_reversed'
This needs to be split up into one-patch-per-subsystem and can not be
taken as-is.
thanks,
greg k-h
WARNING: multiple messages have this Message-ID (diff)
From: Greg KH <gregkh@linuxfoundation.org>
To: kushagra765@outlook.com
Cc: balbi@kernel.org, linux-usb@vger.kernel.org, arnd@arndb.de,
corbet@lwn.net, airlied@linux.ie,
dri-devel@lists.freedesktop.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org, dhowells@redhat.com,
mcgrof@kernel.org, linux-cachefs@redhat.com,
viro@zeniv.linux.org.uk, tzimmermann@suse.de,
akpm@linux-foundation.org
Subject: Re: [ PATCH ] Documentation: fixed doc-build warnings
Date: Sun, 27 Mar 2022 09:11:06 +0200 [thread overview]
Message-ID: <YkAOCrbbrMaYkiSb@kroah.com> (raw)
In-Reply-To: <TYZPR01MB3935D1963BFD458E85412E4DF81B9@TYZPR01MB3935.apcprd01.prod.exchangelabs.com>
On Sat, Mar 26, 2022 at 05:22:55PM +0530, kushagra765@outlook.com wrote:
> >From 9a9918b051d5709b5e14ca8afa29f3ef644b8688 Mon Sep 17 00:00:00 2001
> From: Kushagra Verma <kushagra765@outlook.com>
> Date: Sat, 26 Mar 2022 16:43:15 +0530
> Subject: [PATCH] Documentation: fixed doc-build warnings
This should not be in the body of the email, please fix :(
>
> This patch fixes the following (and 2 other) doc-build warnings:
> 1. ./include/linux/dcache.h:308: warning: expecting prototype for dget, dget_dlock(). Prototype was for dget_dlock() instead
>
> 2. ./include/linux/fscache.h:268: warning: Excess function parameter 'object' description in 'fscache_use_cookie'
>
> 3 ./include/linux/fscache.h:285: warning: Excess function parameter 'object' description in 'fscache_unuse_cookie'
>
> 4. ./drivers/gpu/drm/drm_format_helper.c:640: warning: Excess function parameter 'src' description in 'drm_fb_xrgb8888_to_mono_reversed'
This needs to be split up into one-patch-per-subsystem and can not be
taken as-is.
thanks,
greg k-h
next prev parent reply other threads:[~2022-03-27 7:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-26 11:52 [ PATCH ] Documentation: fixed doc-build warnings kushagra765
2022-03-26 11:52 ` kushagra765
2022-03-27 7:11 ` Greg KH [this message]
2022-03-27 7:11 ` Greg KH
2022-03-28 12:25 ` David Howells
2022-03-28 12:25 ` David Howells
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=YkAOCrbbrMaYkiSb@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=airlied@linux.ie \
--cc=akpm@linux-foundation.org \
--cc=arnd@arndb.de \
--cc=balbi@kernel.org \
--cc=corbet@lwn.net \
--cc=daniel@ffwll.ch \
--cc=dhowells@redhat.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=kushagra765@outlook.com \
--cc=linux-cachefs@redhat.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mcgrof@kernel.org \
--cc=mripard@kernel.org \
--cc=tzimmermann@suse.de \
--cc=viro@zeniv.linux.org.uk \
/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.