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: Patchwork and em28xx delegates
Date: Mon, 15 Apr 2013 23:02:51 +0200 [thread overview]
Message-ID: <516C6AFB.1060601@googlemail.com> (raw)
In-Reply-To: <20130415135018.3a867598@redhat.com>
Am 15.04.2013 18:50, schrieb Mauro Carvalho Chehab:
> Em Mon, 15 Apr 2013 18:41:44 +0200
> Frank Schäfer <fschaefer.oss@googlemail.com> escreveu:
>
>> I've just noticed that my 2 pending em28xx patches have got delegate
>> assigned:
>>
>> https://patchwork.linuxtv.org/patch/17834/
>> => delegated to mkrufky
>>
>> https://patchwork.linuxtv.org/patch/17928/ (Obsoleted)
>> => delegated to hverkuil
>>
>> Ist this a patchwork failure or is the new submaintainers workflow the
>> reason ?
> Sub-maintainers workflow. We expect that most patches will be applied via
> one of the sub-maintainers. That will likely improve Kernel's quality and
> help to reduce the maintainers overload.
How is the em28xx driver split betweend the submaintainers ?
Where should I send em28xx patches in the future ? You are still the
em28xx maintainer, right ?
Regards,
Frank
next prev parent reply other threads:[~2013-04-15 21:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-15 16:41 Patchwork and em28xx delegates Frank Schäfer
2013-04-15 16:50 ` Mauro Carvalho Chehab
2013-04-15 21:02 ` Frank Schäfer [this message]
2013-04-15 21:34 ` Mauro Carvalho Chehab
[not found] ` <CAOcJUbzin_70-mO44S_2b90gjOH4H64g29rO78eMxsmpshu5KQ@mail.gmail.com>
2013-04-17 11:09 ` Michael Krufky
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=516C6AFB.1060601@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.