From: "Markus Rechberger" <mrechberger@gmail.com>
To: "Pekka Enberg" <penberg@cs.helsinki.fi>
Cc: "Devin Heitmueller" <devin.heitmueller@gmail.com>,
"Hans Verkuil" <hverkuil@xs4all.nl>,
v4l <video4linux-list@redhat.com>,
linux-dvb@linuxtv.org,
"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
em28xx <em28xx@mcentral.de>, "Greg KH" <greg@kroah.com>,
mchehab@infradead.org
Subject: Re: [linux-dvb] [PATCH 1/7] Adding empia base driver
Date: Sat, 1 Nov 2008 18:55:36 +0100 [thread overview]
Message-ID: <d9def9db0811011055x7d75b705oa1facb09834bd1c5@mail.gmail.com> (raw)
In-Reply-To: <84144f020811010929q579bebd7p8760d34631df2fd4@mail.gmail.com>
On Sat, Nov 1, 2008 at 5:29 PM, Pekka Enberg <penberg@cs.helsinki.fi> wrote:
> On Sat, Nov 1, 2008 at 6:19 PM, Devin Heitmueller
> <devin.heitmueller@gmail.com> wrote:
>> The reality is that from a technical standpoint I really want Markus
>> to be the maintainer. He knows more about the devices than anyone,
>> works for the vendor, and has access to all the datasheets. That
>> said, I don't want a situation where he is the *only* one who can do
>> work on the codebase because it is poorly commented and structured in
>> a way where only he can understand why it works the way it does.
>> Also, I believe certain design decisions should be made as a result of
>> consensus with the other maintainers, taking into consideration
>> consistency across drivers.
>
> I can understand that you want him to be the maintainer. But so far he
> hasn't really shown to be interested in doing that. It's just bit sad
> that the we don't have a proper driver given that the code exists and
> that there's a person who's willing to do the work to get it merged...
>
There's alot discussion and I haven't followed it yet although, the
best way to go
seen from my side is to take the em28xx-new code and merge the usable kernelcode
into that one (note that only ~10% of the devices in the kernel em28xx
driver are actually
tested).
I read about the License, I can say this is no issue overall, all of
the code is available under GPL,
and some of it is also under BSD license.
I need to catch up the other mails before continuing...
Markus
next prev parent reply other threads:[~2008-11-01 17:55 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-01 14:05 Hans Verkuil
2008-11-01 14:36 ` [linux-dvb] " Andy Walls
2008-11-01 15:46 ` Devin Heitmueller
2008-11-01 16:08 ` Pekka Enberg
2008-11-01 16:19 ` Devin Heitmueller
2008-11-01 16:29 ` Pekka Enberg
2008-11-01 17:55 ` Markus Rechberger [this message]
2008-11-01 16:21 ` Hans Verkuil
2008-11-01 16:27 ` Pekka Enberg
2008-11-01 16:51 ` Devin Heitmueller
2008-11-02 4:02 ` Markus Rechberger
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=d9def9db0811011055x7d75b705oa1facb09834bd1c5@mail.gmail.com \
--to=mrechberger@gmail.com \
--cc=devin.heitmueller@gmail.com \
--cc=em28xx@mcentral.de \
--cc=greg@kroah.com \
--cc=hverkuil@xs4all.nl \
--cc=linux-dvb@linuxtv.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mchehab@infradead.org \
--cc=penberg@cs.helsinki.fi \
--cc=video4linux-list@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
all inboxes | Powered by JetHome®