All of lore.kernel.org
 help / color / mirror / Atom feed
From: Randy Dunlap <randy.dunlap@oracle.com>
To: linux-nfs@vger.kernel.org
Cc: "J. Bruce Fields" <bfields@fieldses.org>,
	Neil Brown <neilb@suse.de>,
	Trond Myklebust <Trond.Myklebust@netapp.com>,
	David Miller <davem@davemloft.net>
Subject: [PATCH] sunrpc: fix missing kernel-doc
Date: Wed, 24 Jun 2009 10:53:07 -0700	[thread overview]
Message-ID: <4A426803.4050807@oracle.com> (raw)

From: Randy Dunlap <randy.dunlap@oracle.com>

Fix sunrpc kernel-doc warnings:

Warning(net/sunrpc/clnt.c:629): No description found for parameter 'req'
Warning(net/sunrpc/clnt.c:629): No description found for parameter 'tk_ops'
Warning(net/sunrpc/clnt.c:629): Excess function parameter 'ops' description in 'rpc_run_bc_task'

Signed-off-by: Randy Dunlap <randy.dunlap@oracle.com>
---
 net/sunrpc/clnt.c |    3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

--- linux-2.6.30-git22.orig/net/sunrpc/clnt.c
+++ linux-2.6.30-git22/net/sunrpc/clnt.c
@@ -622,7 +622,8 @@ EXPORT_SYMBOL_GPL(rpc_call_async);
 /**
  * rpc_run_bc_task - Allocate a new RPC task for backchannel use, then run
  * rpc_execute against it
- * @ops: RPC call ops
+ * @req: the RPC request
+ * @tk_ops: RPC call ops
  */
 struct rpc_task *rpc_run_bc_task(struct rpc_rqst *req,
 					const struct rpc_call_ops *tk_ops)



-- 
~Randy
LPC 2009, Sept. 23-25, Portland, Oregon
http://linuxplumbersconf.org/2009/

             reply	other threads:[~2009-06-24 17:53 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-24 17:53 Randy Dunlap [this message]
  -- strict thread matches above, loose matches on Subject: below --
2008-04-25 15:57 [PATCH] sunrpc: fix missing kernel-doc Randy Dunlap
2008-04-27  5:59 ` David Miller

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=4A426803.4050807@oracle.com \
    --to=randy.dunlap@oracle.com \
    --cc=Trond.Myklebust@netapp.com \
    --cc=bfields@fieldses.org \
    --cc=davem@davemloft.net \
    --cc=linux-nfs@vger.kernel.org \
    --cc=neilb@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.