From: Greg KH <greg@kroah.com>
To: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Cc: Joseph Salisbury <joseph.salisbury@canonical.com>,
linux-kernel@vger.kernel.org, m.chehab@samsung.com,
linux-media@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH 1/1] [media] uvcvideo: quirk PROBE_DEF for Dell SP2008WFP monitor.
Date: Thu, 29 Aug 2013 21:00:21 -0700 [thread overview]
Message-ID: <20130830040021.GA31290@kroah.com> (raw)
In-Reply-To: <3172143.JtUQzMAjLG@avalon>
On Fri, Aug 30, 2013 at 02:41:17AM +0200, Laurent Pinchart wrote:
> Hi Joseph,
>
> Thank you for the patch.
>
> On Thursday 29 August 2013 11:17:41 Joseph Salisbury wrote:
> > BugLink: http://bugs.launchpad.net/bugs/1217957
> >
> > Add quirk for Dell SP2008WFP monitor: 05a9:2641
> >
> > Signed-off-by: Joseph Salisbury <joseph.salisbury@canonical.com>
> > Tested-by: Christopher Townsend <christopher.townsend@canonical.com>
> > Cc: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
> > Cc: Mauro Carvalho Chehab <m.chehab@samsung.com>
> > Cc: linux-media@vger.kernel.org
> > Cc: linux-kernel@vger.kernel.org
> > Cc: stable@vger.kernel.org
>
> Acked-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
>
> I've applied it to my tree. Given that we're too close to the v3.12 merge
> window I will push it for v3.13.
A quirk has to wait that long? That's not ok, they should go in much
sooner than that...
thanks,
greg k-h
next prev parent reply other threads:[~2013-08-30 4:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <cover.1377781889.git.joseph.salisbury@canonical.com>
2013-08-29 15:17 ` [PATCH 1/1] [media] uvcvideo: quirk PROBE_DEF for Dell SP2008WFP monitor Joseph Salisbury
2013-08-30 0:41 ` Laurent Pinchart
2013-08-30 4:00 ` Greg KH [this message]
2013-08-30 10:28 ` Laurent Pinchart
2013-08-30 16:39 ` Greg KH
2013-08-30 16:45 ` Laurent Pinchart
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=20130830040021.GA31290@kroah.com \
--to=greg@kroah.com \
--cc=joseph.salisbury@canonical.com \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=m.chehab@samsung.com \
--cc=stable@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).