linux-kernel - Re: linux-next: Tree for February 1 [ staging/usbvideo/vicam.c: error: expected ‘;’ before ‘)’ token ]

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, 1 Feb 2011 12:58:48 +0100
From:	Sedat Dilek <sedat.dilek@...glemail.com>
To:	Timo von Holtz <tvh@...ormatik.uni-kiel.de>
Cc:	linux-next@...r.kernel.org, LKML <linux-kernel@...r.kernel.org>,
	Greg KH <gregkh@...e.de>,
	Stephen Rothwell <sfr@...b.auug.org.au>
Subject: Re: linux-next: Tree for February 1 [ staging/usbvideo/vicam.c: error: expected ‘;’ before ‘)’ token ]

On Tue, Feb 1, 2011 at 9:32 AM, Sedat Dilek <sedat.dilek@...glemail.com> wrote:
> On Tue, Feb 1, 2011 at 5:34 AM, Stephen Rothwell <sfr@...b.auug.org.au> wrote:
>> Hi all,
>>
>> Changes since 20110131:
>>
>> Dropped tree: xen
>>
>> The tty.current tree lost its conflict.
>>
>> The slab tree still has its build failure so I used the version from
>> next-20110121.
>>
>> The suspend tree lost its build failure.
>>
>> The sparc64 defconfig build has been fixed.
>>
>> The powerpc allyesconfig build has been broken by some obscure bloating
>> of the low memory code.
>>
>> ----------------------------------------------------------------------------
>
> [ CC greg-kh ]
>
> Build error:
> ...
> drivers/staging/usbvideo/vicam.c:222:57: error: expected ‘;’ before ‘)’ token
> drivers/staging/usbvideo/vicam.c:222:57: error: expected statement
> before ‘)’ token
> ...
>
> This should be fixed by:
>
> Index: linux-next-20110201/drivers/staging/usbvideo/vicam.c
> ===================================================================
> --- linux-next-20110201.orig/drivers/staging/usbvideo/vicam.c
> +++ linux-next-20110201/drivers/staging/usbvideo/vicam.c
> @@ -219,7 +219,7 @@ set_camera_power(struct vicam_camera *ca
>  {
>        int status;
>
> -       status = send_control_msg(cam, 0x50, state, 0, NULL, 0));
> +       status = send_control_msg(cam, 0x50, state, 0, NULL, 0);
>        if (status < 0)
>                return status;
>
> - Sedat -
>

[ Changed... TO Timo von Holtz + CC sfr ]

Just FYI:

The problem was introduced in staging-next GIT branch:

commit 046d747e0d2cb597e0b6fa4a79c32b43e97ed792
"taging: usbvideo: vicam: fixed some coding style issues"

- Sedat -

[1] http://git.kernel.org/?p=linux/kernel/git/gregkh/staging-2.6.git;a=commit;h=046d747e0d2cb597e0b6fa4a79c32b43e97ed792
--
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/