linux-kernel - RE: linux-next: Tree for Jun 7 (staging/ccg #2)

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 for Android: free password hash cracker in your pocket

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

Message-id: <000001cd47ae$6d482a60$47d87f20$%p@samsung.com>
Date:	Mon, 11 Jun 2012 10:44:28 +0200
From:	Andrzej Pietrasiewicz <andrzej.p@...sung.com>
To:	'Alan Stern' <stern@...land.harvard.edu>,
	'Randy Dunlap' <rdunlap@...otime.net>
Cc:	'Stephen Rothwell' <sfr@...b.auug.org.au>,
	linux-next@...r.kernel.org, 'LKML' <linux-kernel@...r.kernel.org>,
	'USB list' <linux-usb@...r.kernel.org>,
	devel@...verdev.osuosl.org,
	'Greg Kroah-Hartman' <gregkh@...uxfoundation.org>,
	'Mike Lockwood' <lockwood@...roid.com>
Subject: RE: linux-next: Tree for Jun 7 (staging/ccg #2)

Hello,

On Thursday, June 07, 2012 10:59 PM Alan Stern wrote:

<snip>
> 
> The problems above are caused by the fact that
> drivers/staging/ccg/Kconfig does not make USB_G_CGG dependent on BLOCK.

@Randy: Thanks for finding it.

@Alan: Thanks for suggesting a solution.

> 
> > In file included from drivers/staging/ccg/ccg.c:59:0:
> > drivers/staging/ccg/../../usb/gadget/f_fs.c: At top level:
> > drivers/staging/ccg/../../usb/gadget/f_fs.c:40:0: warning: "pr_vdebug"
> redefined
> > drivers/staging/ccg/../../usb/gadget/u_serial.c:138:0: note: this is the
> location of the previous definition
> 
> This could be fixed by adding a #ifndef guard to f_fs.c and u_serial.c.
> It's a little awkward to combine independent source files this way.
> 
@Randy: Thanks for finding it.

@Alan: Thanks for suggesting a solution.

The patches are on their way.

Andrzej


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