From: David Howells <dhowells@redhat.com>
To: kushagra765@outlook.com
Cc: dhowells@redhat.com, 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, gregkh@linuxfoundation.org, 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: Mon, 28 Mar 2022 13:25:39 +0100 [thread overview]
Message-ID: <2581031.1648470339@warthog.procyon.org.uk> (raw)
In-Reply-To: <TYZPR01MB3935D1963BFD458E85412E4DF81B9@TYZPR01MB3935.apcprd01.prod.exchangelabs.com>
kushagra765@outlook.com wrote:
> @@ -256,7 +256,6 @@ struct fscache_cookie *fscache_acquire_cookie(struct fscache_volume *volume,
>
> /**
> * fscache_use_cookie - Request usage of cookie attached to an object
> - * @object: Object description
> * @will_modify: If cache is expected to be modified locally
> *
> * Request usage of the cookie attached to an object. The caller should tell
> @@ -272,7 +271,6 @@ static inline void fscache_use_cookie(struct fscache_cookie *cookie,
>
> /**
> * fscache_unuse_cookie - Cease usage of cookie attached to an object
> - * @object: Object description
> * @aux_data: Updated auxiliary data (or NULL)
> * @object_size: Revised size of the object (or NULL)
> *
Just deleting these lines is the wrong thing to do. They should instead
mention the cookie parameter.
David
prev parent reply other threads:[~2022-03-28 12:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-26 11:52 [ PATCH ] Documentation: fixed doc-build warnings kushagra765
2022-03-27 7:11 ` Greg KH
2022-03-28 12:25 ` David Howells [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=2581031.1648470339@warthog.procyon.org.uk \
--to=dhowells@redhat.com \
--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=dri-devel@lists.freedesktop.org \
--cc=gregkh@linuxfoundation.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 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).