public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: Mauro Carvalho Chehab <mchehab@redhat.com>
To: "Bjørn Mork" <bjorn@mork.no>
Cc: linux-media@vger.kernel.org
Subject: Re: S2-3200 switching-timeouts on 2.6.38
Date: Tue, 22 Mar 2011 07:15:33 -0300	[thread overview]
Message-ID: <4D8876C5.6030802@redhat.com> (raw)
In-Reply-To: <8739mfwkfa.fsf@nemi.mork.no>

Em 22-03-2011 06:53, Bjørn Mork escreveu:
> Manu Abraham <abraham.manu@gmail.com> writes:
>> On Tue, Mar 22, 2011 at 1:46 AM, Randy Dunlap <rdunlap@xenotime.net> wrote:
>>> On Mon, 21 Mar 2011 20:46:23 +0100 Rico Tzschichholz wrote:
>>>
>>>> Hello,
>>>>
>>>> I would like to know if there is any intention to include this patch
>>>> soon? https://patchwork.kernel.org/patch/244201/
>>>
>>> There are MANY posted but unmerged patches in patchwork from the linux-media
>>> mailing list.  What is going on (or not going on) with patch merging?
>>
>> Actually, quite a lot of effort was put in to get that part right. It
>> does the reverse thing that's to be done.
>> The revamped version is here [1] If the issue persists still, then it
>> needs to be investigated further.
>>
>> [1] http://www.mail-archive.com/linuxtv-commits@linuxtv.org/msg09214.html
> 
> So the patch state should be "Rejected" and not "Under Review".
> 
> Would certainly help us all if the patchwork state was updated whenever
> a patch actually was processed...

Yes, but the thing is that somebody needs to manually update me about status change,
as patchwork doesn't provide any way for it. Patchwork's permission for a project
is all or nothing: or you completely own a project, or you have just read-only
access. There's no way, currently, for me to delegate a patch to someone without
allowing that person to touch at the non-delegated patches. Also, patchwork
also doesn't allow me to change contributor status (there's just one global admin
that creates and/or modifies account access on patchwork).

Anyway, I've updated the status for #244201.

Thanks,
Mauro.

  reply	other threads:[~2011-03-22 10:15 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-21 19:46 S2-3200 switching-timeouts on 2.6.38 Rico Tzschichholz
2011-03-21 20:16 ` Randy Dunlap
2011-03-21 20:31   ` Manu Abraham
2011-03-22  9:53     ` Bjørn Mork
2011-03-22 10:15       ` Mauro Carvalho Chehab [this message]
2011-03-22 20:21       ` Manu Abraham
2011-03-22 11:33     ` Rico Tzschichholz
2011-03-22 13:07       ` Bjørn Mork
2011-03-22 20:54       ` Manu Abraham
2011-03-23  7:10         ` Rico Tzschichholz
2011-08-10 23:49 ` P. van Gaans
2011-08-11 20:45   ` P. van Gaans
  -- strict thread matches above, loose matches on Subject: below --
2011-03-23 18:19 H. Ellenberger
2011-03-24 16:57 ` Julian Scheel
2011-03-24 18:32   ` Steffen Barszus
2011-03-24 19:39     ` Julian Scheel
2011-03-25 15:01 Paul Franke
2011-03-25 17:53 ` Manu Abraham
2011-03-25 19:56   ` Paul Franke

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=4D8876C5.6030802@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