From: Sebastian Ott <sebott@linux.vnet.ibm.com>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Peter Oberparleiter <oberpar@linux.vnet.ibm.com>,
linux-s390@vger.kernel.org,
Martin Schwidefsky <schwidefsky@de.ibm.com>,
Heiko Carstens <heiko.carstens@de.ibm.com>,
linux390@de.ibm.com
Subject: Re: [PATCH] s390: fix new ccwgroup.h kernel-doc warning
Date: Mon, 14 Apr 2014 21:28:24 +0200 (CEST) [thread overview]
Message-ID: <alpine.LFD.2.11.1404142127070.1561@denkbrett> (raw)
In-Reply-To: <534C1DC9.7020108@infradead.org>
On Mon, 14 Apr 2014, Randy Dunlap wrote:
> From: Randy Dunlap <rdunlap@infradead.org>
>
> Fix new s390 kernel-doc warning:
>
> Warning(arch/s390/include/asm/ccwgroup.h:27): No description found for parameter 'ungroup_work'
>
> Signed-off-by: Randy Dunlap <rdunlap@infradead.org>
> Cc: Sebastian Ott <sebott@linux.vnet.ibm.com>
> Cc: Peter Oberparleiter <oberpar@linux.vnet.ibm.com>
> Cc: linux-s390@vger.kernel.org
> Cc: Martin Schwidefsky <schwidefsky@de.ibm.com>
> Cc: Heiko Carstens <heiko.carstens@de.ibm.com>
> Cc: linux390@de.ibm.com
> ---
> arch/s390/include/asm/ccwgroup.h | 2 ++
> 1 file changed, 2 insertions(+)
>
> --- lnx-315-rc1.orig/arch/s390/include/asm/ccwgroup.h
> +++ lnx-315-rc1/arch/s390/include/asm/ccwgroup.h
> @@ -10,6 +10,8 @@ struct ccw_driver;
> * @count: number of attached slave devices
> * @dev: embedded device structure
> * @cdev: variable number of slave devices, allocated as needed
> + * @ungroup_work: work to be done when a ccwgroup notifier has action
> + * type %BUS_NOTIFY_UNBIND_DRIVER
> */
> struct ccwgroup_device {
> enum {
>
>
Applied, thanks!
Sebastian
prev parent reply other threads:[~2014-04-14 19:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-14 17:41 Randy Dunlap
2014-04-14 19:28 ` Sebastian Ott [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=alpine.LFD.2.11.1404142127070.1561@denkbrett \
--to=sebott@linux.vnet.ibm.com \
--cc=akpm@linux-foundation.org \
--cc=heiko.carstens@de.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=linux390@de.ibm.com \
--cc=oberpar@linux.vnet.ibm.com \
--cc=rdunlap@infradead.org \
--cc=schwidefsky@de.ibm.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
all inboxes | Powered by JetHome®