public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: Mauro Carvalho Chehab <mchehab@redhat.com>
To: "Frank Schäfer" <fschaefer.oss@googlemail.com>
Cc: Linux Media Mailing List <linux-media@vger.kernel.org>
Subject: Re: Patch update notification: 2 patches updated
Date: Wed, 6 Feb 2013 13:58:55 -0200	[thread overview]
Message-ID: <20130206135855.48b74ffb@redhat.com> (raw)
In-Reply-To: <5112782A.5000706@googlemail.com>

Em Wed, 06 Feb 2013 16:35:06 +0100
Frank Schäfer <fschaefer.oss@googlemail.com> escreveu:

> Am 05.02.2013 23:08, schrieb Mauro Carvalho Chehab:
> > Em Tue, 05 Feb 2013 22:46:10 +0100
> > Frank Schäfer <fschaefer.oss@googlemail.com> escreveu:
> >
> >> Am 05.02.2013 22:33, schrieb Patchwork:
> >>> Hello,
> >>>
> >>> The following patches (submitted by you) have been updated in patchwork:
> >> ...
> >>>  * [RFC] em28xx: fix analog streaming with USB bulk transfers
> >>>      - http://patchwork.linuxtv.org/patch/16197/
> >>>     was: New
> >>>     now: RFC
> >> What's your plan with this patch ?
> >> We have this regression in the media-tree since a few weeks now.
> >> Nobody replied to it or came up with a better solution...
> > Well, you tagged it as RFC. I just marked as such at patchwork. I don't even
> > read patches tagged as [RFC] or [REVIEW],
> 
> Uhm... even patches which are sent to you as the maintainer of the
> _driver_ ?
> Isn't commenting / reviewing patches the maintainers job ?
> 
> 
> >  as those patches will be
> > resubmitted later by the patch author, if they're ok, or a new version will
> > be sent instead.
> 
> That's what I'm asking you. Is this patch ok / ready ?
> Or can I generally conclude that patches are fine when there is no
> reaction on them ?

Frank,

As you may notice, my main "job" with regards to media stuff is to be
the media core maintainer. My work as a driver maintainer or as a
developer is forced to go to a second plane, as my time is limited.
So, I generally trust that driver developers are doing the right
thing.

ATM, I won't have anytime soon to test patches. So, if those patches 
require any test from me, they'll need to be postponed to 3.10, as I'm
finishing the handling of the patches for 3.9 today.

Also, from my side, there are simply too much patches sent to me, either
on my inbox (where I never read) and/or at linux-media ML. The last ones
I get from patchwork. Sometimes, even before picking the patches, I tag
everything with RFC or REVIEW on it as RFC. Then I handle the remaining
ones. This is to reduce the load to an acceptable work queue.

So, if you think that the USB patches are ok, just send it to the ML
without tagging it, and I'll analyze and apply if I believe that they're
ok. I'll eventually test the em28xx driver later, when I found some time.

If otherwise you think they may not be ready yet, the better to wait
for Devin to test, if it has some time, or send me a separate email asking
for me to test the patches.

Regards,
Mauro

  reply	other threads:[~2013-02-06 15:59 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20130205213301.13968.54926@www.linuxtv.org>
2013-02-05 21:46 ` Patch update notification: 2 patches updated Frank Schäfer
2013-02-05 22:08   ` Mauro Carvalho Chehab
2013-02-06 15:35     ` Frank Schäfer
2013-02-06 15:58       ` Mauro Carvalho Chehab [this message]
2013-02-06 17:30         ` Frank Schäfer
     [not found] <20130420121301.2461.37868@www.linuxtv.org>
2013-04-22 10:50 ` Prabhakar Lad
2013-04-23  6:41   ` Hans Verkuil
2013-04-23  8:14     ` Prabhakar Lad

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=20130206135855.48b74ffb@redhat.com \
    --to=mchehab@redhat.com \
    --cc=fschaefer.oss@googlemail.com \
    --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