From: Sebastian Ott <sebott@linux.vnet.ibm.com>
To: Cornelia Huck <cohuck@redhat.com>
Cc: Martin Schwidefsky <schwidefsky@de.ibm.com>,
Heiko Carstens <heiko.carstens@de.ibm.com>,
corbet@lwn.net, oberpar@linux.vnet.ibm.com,
linux-s390@vger.kernel.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 3/3] s390/cmf: fix kerneldoc
Date: Tue, 23 Jan 2018 18:37:35 +0100 (CET) [thread overview]
Message-ID: <alpine.LFD.2.21.1801231833550.1761@schleppi> (raw)
In-Reply-To: <20180123150245.30312-4-cohuck@redhat.com>
On Tue, 23 Jan 2018, Cornelia Huck wrote:
> Make sure we use proper Return sections, and make the output
> for cmf_enable() less odd.
>
> Signed-off-by: Cornelia Huck <cohuck@redhat.com>
> ---
> +++ b/drivers/s390/cio/cmf.c
> @@ -1118,9 +1118,10 @@ int ccw_set_cmf(struct ccw_device *cdev, int enable)
> * enable_cmf() - switch on the channel measurement for a specific device
> * @cdev: The ccw device to be enabled
> *
> - * Returns %0 for success or a negative error value.
> - * Note: If this is called on a device for which channel measurement is already
> - * enabled a reset of the measurement data is triggered.
> + * Enable channel measurements for @cdev. If this is called on a device
> + * for which channel measurement is already enabled a reset of the
> + * measurement data is triggered.
> + * Returns: %0 for success or a negative error value
^
I took the liberty to do re-add the dot at the end..
Applied. Thanks!
next prev parent reply other threads:[~2018-01-23 17:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-23 15:02 [PATCH 0/3] s390: documentation update Cornelia Huck
2018-01-23 15:02 ` [PATCH 1/3] s390/docs: mention subchannel types Cornelia Huck
2018-01-23 15:02 ` [PATCH 2/3] s390/docs: reword airq section Cornelia Huck
2018-01-23 15:02 ` [PATCH 3/3] s390/cmf: fix kerneldoc Cornelia Huck
2018-01-23 17:37 ` Sebastian Ott [this message]
2018-01-24 12:44 ` [PATCH 0/3] s390: documentation update Sebastian Ott
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.21.1801231833550.1761@schleppi \
--to=sebott@linux.vnet.ibm.com \
--cc=cohuck@redhat.com \
--cc=corbet@lwn.net \
--cc=heiko.carstens@de.ibm.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=oberpar@linux.vnet.ibm.com \
--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