linux-kernel - RE: [PATCH 1/5] staging/easycap: Kill leftover build options in readme

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] [thread-next>] [day] [month] [year] [list]

Date:	Mon, 13 Jun 2011 15:24:58 +0300
From:	"Winkler, Tomas" <tomas.winkler@...el.com>
To:	Kirill Smelkov <kirr@....spb.ru>,
	Greg Kroah-Hartman <gregkh@...e.de>
CC:	Mike Thomas <rmthomas@...olus.org>,
	"devel@...verdev.osuosl.org" <devel@...verdev.osuosl.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: RE: [PATCH 1/5] staging/easycap: Kill leftover build options in
 readme



> -----Original Message-----
> From: Kirill Smelkov [mailto:kirr@....spb.ru]
> Sent: Monday, June 13, 2011 3:18 PM
> To: Greg Kroah-Hartman
> Cc: Winkler, Tomas; Mike Thomas; devel@...verdev.osuosl.org; linux-
> kernel@...r.kernel.org; Kirill Smelkov
> Subject: [PATCH 1/5] staging/easycap: Kill leftover build options in readme
> 
> The following options were removed from in-tree driver, but were left in
> README:
> 
> - EASYCAP_IS_VIDEODEV_CLIENT was removed in cb81fa07
> (staging/easycap:
>   kill EASYCAP_IS_VIDEODEV_CLIENT compilation conditional);
> 
> - EASYCAP_NEEDS_V4L2_DEVICE_H/EASYCAP_NEEDS_V4L2_FOPS were
> removed in
>   30516058 (staging/easycap: kill EASYCAP_NEEDS_V4L2_DEVICE_H and
>   EASYCAP_NEEDS_V4L2_FOPS);
> 
> - EASYCAP_NEEDS_UNLOCKED_IOCTL was removed in f2b3c685
> (staging/easycap:
>   kill EASYCAP_NEEDS_UNLOCKED_IOCTL).
> 
> Remove them.
> 
> Cc: Tomas Winkler <tomas.winkler@...el.com>
> Cc: Mike Thomas <rmthomas@...olus.org>
> Signed-off-by: Kirill Smelkov <kirr@....spb.ru>
Acked-by: Tomas Winkler <tomas.winkler@...el.com>

> ---
>  drivers/staging/easycap/README |   22 ----------------------
>  1 files changed, 0 insertions(+), 22 deletions(-)
> 
> diff --git a/drivers/staging/easycap/README
> b/drivers/staging/easycap/README index 6b5ac0d..16b8264 100644
> --- a/drivers/staging/easycap/README
> +++ b/drivers/staging/easycap/README
> @@ -27,28 +27,6 @@ BUILD OPTIONS AND DEPENDENCIES  Unless
> EASYCAP_DEBUG is defined during compilation it will not be possible  to
> select a debug level at the time of module installation.
> 
> -If the parameter EASYCAP_IS_VIDEODEV_CLIENT is undefined during
> compilation -the built module is entirely independent of the videodev
> module, and when -the EasyCAP is physically plugged into a USB port the
> special files
> -/dev/easycap0 and /dev/easysnd1 are created as video and sound sources -
> respectively.
> -
> -If the parameter EASYCAP_IS_VIDEODEV_CLIENT is defined during
> compilation -the built easycap module is configured to register with the
> videodev module, -in which case the special files created when the EasyCAP
> is plugged in are
> -/dev/video0 and /dev/easysnd0.
> -
> -During in-tree builds the following should should be defined whenever the -
> parameter EASYCAP_IS_VIDEODEV_CLIENT is defined:
> -
> -EASYCAP_NEEDS_V4L2_DEVICE_H
> -EASYCAP_NEEDS_V4L2_FOPS
> -EASYCAP_NEEDS_UNLOCKED_IOCTL
> -
> -If the build is performed out-of-tree against older kernels the parameters -
> to be defined depend on the kernel version in a way which will not be -
> discussed here.
> -
> 
>  KNOWN RUNTIME ISSUES
>  --------------------
> --
> 1.7.6.rc1

---------------------------------------------------------------------
Intel Israel (74) Limited

This e-mail and any attachments may contain confidential material for
the sole use of the intended recipient(s). Any review or distribution
by others is strictly prohibited. If you are not the intended
recipient, please contact the sender and delete all copies.

--
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/