From: Mauro Carvalho Chehab <mchehab@redhat.com>
To: "Bjørn Mork" <bjorn@mork.no>
Cc: linux-media@vger.kernel.org
Subject: Re: Status of the patches under review (85 patches) and some misc notes about the devel procedures
Date: Tue, 06 Jul 2010 10:46:46 -0300 [thread overview]
Message-ID: <4C3333C6.60503@redhat.com> (raw)
In-Reply-To: <87y6dv2zn4.fsf@nemi.mork.no>
Em 01-07-2010 08:46, Bjørn Mork escreveu:
> Mauro Carvalho Chehab <mchehab@redhat.com> writes:
>
>
>> My original idea were to send one of such emails per week,
>
> Nearly two months has passed since this message. I apologize if I
> missed something, but I have not seen another status update. Is it just
> me?
>
> Anyway, since the last status I've seen, 2.6.34 has been released, the
> 2.6.35 merge window has been open and then closed, and a number of new
> patches have been collected in
> https://patchwork.kernel.org/project/linux-media/list/
> , many of which seem rather trivial.
Ideally, the patches that are OK should already be catched by a driver
maintainer and submitted me via git or mercurial pull request, and the bad
patches should already be nacked. The ones that are not merged from the
normal process are the ones that are not trivial, among others, due to one
of the reasons bellow:
- there's no driver maintainer;
- the driver maintainer is lazy or overloaded;
- there are some concerns about that patch;
- there are some changes undergoing that will affect/be affected by
the patch;
- the patch got forgotten/lost in the middle of the emails.
The fact is that the number of those patches are very high, causes me a lot
of overload to handle them and to send emails to people requesting the review
of those patches.
> Any chance of a new status update anytime soon?
Updated today, after two or three weeks spent to handle the backlog.
I still have a few pull requests pending for 2.6.35-rc (bug fixes) that I'll
be handling this week.
> I'm particularily
> interested in getting a forced status change on any patch which was
> "under review" at the time of the last status message. I believe it's
> reasonable to expect two months "review" to be more than enough. If
> the patches are found unacceptable, then it's much better to have them
> rejected with a "please fix foo and resubmit" than the current total
> silence called "review".
The patches marked as under review means that I'm expecting an action
from someone else (the patch author or the driver author/maintainer).
So, if you have patches there still under review, you're helping us
if you direct your complains to the one that it is sitting on the top
of them.
Cheers,
Mauro.
next prev parent reply other threads:[~2010-07-06 13:46 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-07 12:39 Status of the patches under review (85 patches) and some misc notes about the devel procedures Mauro Carvalho Chehab
2010-05-07 12:58 ` Guennadi Liakhovetski
2010-05-08 1:13 ` Mauro Carvalho Chehab
2010-05-07 13:03 ` Manu Abraham
2010-05-08 1:27 ` Mauro Carvalho Chehab
2010-05-07 13:10 ` Manu Abraham
2010-05-08 1:26 ` Mauro Carvalho Chehab
2010-05-27 14:05 ` Guy Martin
2010-05-27 21:42 ` Mauro Carvalho Chehab
2010-05-07 13:15 ` Manu Abraham
2010-05-08 1:28 ` Mauro Carvalho Chehab
2010-05-07 13:16 ` Manu Abraham
2010-05-08 1:30 ` Mauro Carvalho Chehab
2010-05-08 5:34 ` Herton Ronaldo Krzesinski
2010-05-08 22:41 ` Mauro Carvalho Chehab
2010-05-10 18:46 ` Herton Ronaldo Krzesinski
2010-05-10 19:54 ` Mauro Carvalho Chehab
2010-05-08 6:31 ` Jean-Francois Moine
2010-05-08 22:45 ` Mauro Carvalho Chehab
2010-05-10 13:45 ` Sarah Sharp
2010-05-10 16:25 ` Mauro Carvalho Chehab
2010-05-10 17:39 ` Jean-Francois Moine
2010-05-11 1:20 ` Sarah Sharp
2010-05-10 6:57 ` Pawel Osciak
2010-05-10 12:58 ` Pawel Osciak
2010-07-01 11:46 ` Bjørn Mork
2010-07-06 13:46 ` Mauro Carvalho Chehab [this message]
2010-07-07 12:52 ` Bjørn Mork
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=4C3333C6.60503@redhat.com \
--to=mchehab@redhat.com \
--cc=bjorn@mork.no \
--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;
as well as URLs for NNTP newsgroup(s).