From: Jonathan Cameron <jic23@cam.ac.uk>
To: Johan Hovold <jhovold@gmail.com>
Cc: Jonathan Cameron <jic23@kernel.org>,
linux-kernel@vger.kernel.org,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-iio@vger.kernel.org
Subject: Re: [PATCH] staging:iio: remove num_interrupt_lines from documentation
Date: Tue, 22 May 2012 13:17:01 +0100 [thread overview]
Message-ID: <4FBB83BD.4020509@cam.ac.uk> (raw)
In-Reply-To: <1337682602-15105-1-git-send-email-jhovold@gmail.com>
On 5/22/2012 11:30 AM, Johan Hovold wrote:
> Commit 5aa9618896e0ba49 ("staging:iio: remove broken support for
> multiple event interfaces.") removed the num_interrupt_lines field from
> struct iio_info but the documentation was never updated.
>
Good catch.
> Signed-off-by: Johan Hovold<jhovold@gmail.com>
Acked-by: Jonathan Cameron <jic23@kernel.org>
> ---
> drivers/staging/iio/Documentation/device.txt | 2 --
> 1 files changed, 0 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/staging/iio/Documentation/device.txt b/drivers/staging/iio/Documentation/device.txt
> index 0338c7c..f03fbd3 100644
> --- a/drivers/staging/iio/Documentation/device.txt
> +++ b/drivers/staging/iio/Documentation/device.txt
> @@ -29,8 +29,6 @@ Then fill in the following:
> * info->driver_module:
> Set to THIS_MODULE. Used to ensure correct ownership
> of various resources allocate by the core.
> - * info->num_interrupt_lines:
> - Number of event triggering hardware lines the device has.
> * info->event_attrs:
> Attributes used to enable / disable hardware events.
> * info->attrs:
prev parent reply other threads:[~2012-05-22 12:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-22 10:30 [PATCH] staging:iio: remove num_interrupt_lines from documentation Johan Hovold
2012-05-22 12:17 ` Jonathan Cameron [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=4FBB83BD.4020509@cam.ac.uk \
--to=jic23@cam.ac.uk \
--cc=gregkh@linuxfoundation.org \
--cc=jhovold@gmail.com \
--cc=jic23@kernel.org \
--cc=linux-iio@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).