From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Guennadi Liakhovetski <g.liakhovetski@gmx.de>
Cc: Linux Media Mailing List <linux-media@vger.kernel.org>,
Hans Verkuil <hverkuil@xs4all.nl>
Subject: Re: Patch review
Date: Wed, 28 Feb 2018 17:21:27 +0200 [thread overview]
Message-ID: <1552444.87XHR44T4u@avalon> (raw)
In-Reply-To: <alpine.DEB.2.20.1802281559500.29266@axis700.grange>
Hi Guennadi,
On Wednesday, 28 February 2018 17:07:00 EET Guennadi Liakhovetski wrote:
> Hi,
>
> I know the "development process and responsibilities" was the main topic
> during the last media summit. Unfortunately I haven't attended it, from
> the etherpad notes I also cannot quite conclude what decisions have been
> made. Have any measures been discussed and agreed upon for cases, when
> patches don't get reviewed for many months, adding up to more than a year
> (in this specific case the first version submitted in June 2016)?
I assume you're talking about the "[PATCH 0/2 v6] uvcvideo: asynchronous
controls" series, is that correct ?
--
Regards,
Laurent Pinchart
next prev parent reply other threads:[~2018-02-28 15:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-28 15:07 Patch review Guennadi Liakhovetski
2018-02-28 15:21 ` Laurent Pinchart [this message]
2018-02-28 15:49 ` Guennadi Liakhovetski
2018-03-08 16:49 ` Mauro Carvalho Chehab
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=1552444.87XHR44T4u@avalon \
--to=laurent.pinchart@ideasonboard.com \
--cc=g.liakhovetski@gmx.de \
--cc=hverkuil@xs4all.nl \
--cc=linux-media@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