linux-kernel - Re: [PATCH] usb: gadget: fix sparse warnings

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]

Message-ID: <20150223152254.GA32701@saruman.tx.rr.com>
Date:	Mon, 23 Feb 2015 09:22:54 -0600
From:	Felipe Balbi <balbi@...com>
To:	Laurent Pinchart <laurent.pinchart@...asonboard.com>
CC:	<balbi@...com>, Lad Prabhakar <prabhakar.csengg@...il.com>,
	Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
	<linux-usb@...r.kernel.org>, <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] usb: gadget: fix sparse warnings

On Sun, Feb 08, 2015 at 05:46:38PM +0200, Laurent Pinchart wrote:
> Hi Felipe,
> 
> On Thursday 05 February 2015 12:08:09 Felipe Balbi wrote:
> > On Thu, Feb 05, 2015 at 05:02:46PM +0200, Laurent Pinchart wrote:
> > > Hi Prabhakar,
> > > 
> > > Thank you for the patch.
> > > 
> > > On Thursday 05 February 2015 13:02:18 Lad Prabhakar wrote:
> > > > From: "Lad, Prabhakar" <prabhakar.csengg@...il.com>
> > > > 
> > > > this patch fixes following sparse warnings:
> > > > 
> > > > uvc_video.c:283:5: warning: symbol 'uvcg_video_pump' was not declared.
> > > > Should it be static? uvc_video.c:342:5: warning: symbol
> > > > 'uvcg_video_enable'
> > > > was not declared. Should it be static? uvc_video.c:381:5: warning:
> > > > symbol
> > > > 'uvcg_video_init' was not declared. Should it be static?
> > > > 
> > > > Signed-off-by: Lad, Prabhakar <prabhakar.csengg@...il.com>
> > > 
> > > Acked-by: Laurent Pinchart <laurent.pinchart@...asonboard.com>
> > > 
> > > Felipe, could you please take this in your tree ?
> > 
> > my tree is closed for v3.20. I'll pick it up once -rc1 is out
> 
> That's good, I was targeting v3.21 too. How do you usually ensure that patches 
> don't get lost, do you apply them to a n+1 branch straight away (which is what 
> I was asking in my previous mail), rely on patchwork or some similar tool, or 
> expect developers to ping you again when -rc1 is out ?

I leave the email unread in another maildir

-- 
balbi

Download attachment "signature.asc" of type "application/pgp-signature" (820 bytes)