linux-kernel - Re: [PATCH] staging:iio: remove num_interrupt

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:	Tue, 22 May 2012 13:17:01 +0100
From:	Jonathan Cameron <jic23@....ac.uk>
To:	Johan Hovold <jhovold@...il.com>
CC:	Jonathan Cameron <jic23@...nel.org>, linux-kernel@...r.kernel.org,
	Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
	linux-iio@...r.kernel.org
Subject: Re: [PATCH] staging:iio: remove num_interrupt_lines from documentation

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@...il.com>
Acked-by: Jonathan Cameron <jic23@...nel.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:

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/