From: Sebastian Reichel <sre@kernel.org>
To: Javier Martinez Canillas <javier@osg.samsung.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] HSI: Remove struct hsi_client private fields from kernel-doc
Date: Sat, 21 Nov 2015 18:46:56 +0100 [thread overview]
Message-ID: <20151121174655.GA2976@earth> (raw)
In-Reply-To: <1444288308-11469-1-git-send-email-javier@osg.samsung.com>
[-- Attachment #1: Type: text/plain, Size: 955 bytes --]
Hi,
On Thu, Oct 08, 2015 at 09:11:48AM +0200, Javier Martinez Canillas wrote:
> The kernel-doc how to says that structure fields that are inside a
> "private:" area shouldn't be listed in the generated documentation
> but the private fields for struct hsi_client private are listed.
>
> This also fixes the following make htmldocs warnings:
>
> .//include/linux/hsi/hsi.h:150: warning: Excess struct/union/enum/typedef member 'e_handler' description in 'hsi_client'
> .//include/linux/hsi/hsi.h:150: warning: Excess struct/union/enum/typedef member 'pclaimed' description in 'hsi_client'
> .//include/linux/hsi/hsi.h:150: warning: Excess struct/union/enum/typedef member 'nb' description in 'hsi_client'
>
> Signed-off-by: Javier Martinez Canillas <javier@osg.samsung.com>
Thanks, queued:
https://git.kernel.org/cgit/linux/kernel/git/sre/linux-hsi.git/commit/?h=for-next&id=403c5c0650816375527a6feecfb255d9b494dda3
-- Sebastian
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
prev parent reply other threads:[~2015-11-21 17:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-08 7:11 [PATCH] HSI: Remove struct hsi_client private fields from kernel-doc Javier Martinez Canillas
2015-11-13 17:08 ` Javier Martinez Canillas
2015-11-13 22:06 ` Sebastian Reichel
2015-11-21 17:46 ` Sebastian Reichel [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=20151121174655.GA2976@earth \
--to=sre@kernel.org \
--cc=javier@osg.samsung.com \
--cc=linux-kernel@vger.kernel.org \
/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