From: "Frank Schäfer" <fschaefer.oss@googlemail.com>
To: Mauro Carvalho Chehab <mchehab@redhat.com>
Cc: Linux Media Mailing List <linux-media@vger.kernel.org>
Subject: Re: Patch update notification: 2 patches updated
Date: Wed, 06 Feb 2013 16:35:06 +0100 [thread overview]
Message-ID: <5112782A.5000706@googlemail.com> (raw)
In-Reply-To: <20130205200859.3ab68dd3@redhat.com>
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 ?
Regards,
Frank
next prev parent reply other threads:[~2013-02-06 15:34 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 [this message]
2013-02-06 15:58 ` Mauro Carvalho Chehab
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=5112782A.5000706@googlemail.com \
--to=fschaefer.oss@googlemail.com \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox