From: David Miller <davem@davemloft.net>
To: randy.dunlap@oracle.com
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH 2/3] net/sock.h: add missing kernel-doc notation
Date: Tue, 10 Aug 2010 00:09:51 -0700 (PDT) [thread overview]
Message-ID: <20100810.000951.28795076.davem@davemloft.net> (raw)
In-Reply-To: <20100809164107.a992561a.randy.dunlap@oracle.com>
From: Randy Dunlap <randy.dunlap@oracle.com>
Date: Mon, 9 Aug 2010 16:41:07 -0700
> From: Randy Dunlap <randy.dunlap@oracle.com>
>
> Add missing kernel-doc notation to struct sock:
>
> Warning(include/net/sock.h:324): No description found for parameter 'sk_peer_pid'
> Warning(include/net/sock.h:324): No description found for parameter 'sk_peer_cred'
> Warning(include/net/sock.h:324): No description found for parameter 'sk_classid'
> Warning(include/net/sock.h:324): Excess struct/union/enum/typedef member 'sk_peercred' description in 'sock'
>
> Signed-off-by: Randy Dunlap <randy.dunlap@oracle.com>
Applied.
prev parent reply other threads:[~2010-08-10 7:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-09 23:41 [PATCH 2/3] net/sock.h: add missing kernel-doc notation Randy Dunlap
2010-08-10 7:09 ` David Miller [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=20100810.000951.28795076.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=randy.dunlap@oracle.com \
/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).