From: Felipe Balbi <balbi@ti.com>
To: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Cc: <balbi@ti.com>, Lad Prabhakar <prabhakar.csengg@gmail.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
<linux-usb@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] usb: gadget: fix sparse warnings
Date: Mon, 23 Feb 2015 09:22:54 -0600 [thread overview]
Message-ID: <20150223152254.GA32701@saruman.tx.rr.com> (raw)
In-Reply-To: <2766350.VUtuXuN7Av@avalon>
[-- Attachment #1: Type: text/plain, Size: 1483 bytes --]
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@gmail.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@gmail.com>
> > >
> > > Acked-by: Laurent Pinchart <laurent.pinchart@ideasonboard.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
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2015-02-23 15:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-05 13:02 [PATCH] usb: gadget: fix sparse warnings Lad Prabhakar
2015-02-05 15:02 ` Laurent Pinchart
2015-02-05 18:08 ` Felipe Balbi
2015-02-08 15:46 ` Laurent Pinchart
2015-02-23 15:22 ` Felipe Balbi [this message]
-- strict thread matches above, loose matches on Subject: below --
2015-02-05 13:11 Lad Prabhakar
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20150223152254.GA32701@saruman.tx.rr.com \
--to=balbi@ti.com \
--cc=gregkh@linuxfoundation.org \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=prabhakar.csengg@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.