From: Jonathan Cameron <jic23@kernel.org>
To: "Tobin C. Harding" <me@tobin.cc>
Cc: Hartmut Knaack <knaack.h@gmx.de>,
Lars-Peter Clausen <lars@metafoo.de>,
Peter Meerwald-Stadler <pmeerw@pmeerw.net>,
linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 1/2] iio: add kernel-doc for field @owner
Date: Sun, 7 Jan 2018 16:13:27 +0000 [thread overview]
Message-ID: <20180107161327.241e6eec@archlinux> (raw)
In-Reply-To: <1515275766-31302-2-git-send-email-me@tobin.cc>
On Sun, 7 Jan 2018 08:56:05 +1100
"Tobin C. Harding" <me@tobin.cc> wrote:
> When building kernel documentation sphinx emits the following warning
>
> warning: No description found for parameter 'owner'
>
> Add description for struct member 'owner'.
>
> Signed-off-by: Tobin C. Harding <me@tobin.cc>
Applied to the togreg branch of iio.git and pushed out as testing for
the autobuilders to play with it.
Thanks,
Jonathan
> ---
> include/linux/iio/trigger.h | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/include/linux/iio/trigger.h b/include/linux/iio/trigger.h
> index 7d5e44518379..390789d43369 100644
> --- a/include/linux/iio/trigger.h
> +++ b/include/linux/iio/trigger.h
> @@ -43,6 +43,7 @@ struct iio_trigger_ops {
> /**
> * struct iio_trigger - industrial I/O trigger device
> * @ops: [DRIVER] operations structure
> + * @owner: [INTERN] owner of this driver module
> * @id: [INTERN] unique id number
> * @name: [DRIVER] unique name
> * @dev: [DRIVER] associated device (if relevant)
next prev parent reply other threads:[~2018-01-07 16:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-06 21:56 [PATCH v3 0/2] fix kernel-docs for struct iio_trigger Tobin C. Harding
2018-01-06 21:56 ` [PATCH v3 1/2] iio: add kernel-doc for field @owner Tobin C. Harding
2018-01-07 16:13 ` Jonathan Cameron [this message]
2018-01-06 21:56 ` [PATCH v3 2/2] iio: add field identifier for @use_count kernel-doc Tobin C. Harding
2018-01-07 16:15 ` Jonathan Cameron
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=20180107161327.241e6eec@archlinux \
--to=jic23@kernel.org \
--cc=knaack.h@gmx.de \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=me@tobin.cc \
--cc=pmeerw@pmeerw.net \
/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.