From: Mauro Carvalho Chehab <mchehab@redhat.com>
To: "Bjørn Mork" <bjorn@mork.no>
Cc: linux-media@vger.kernel.org
Subject: Re: linuxtv.org Wiki (was Re: cx23885 module)
Date: Sat, 23 Oct 2010 11:26:21 -0200 [thread overview]
Message-ID: <4CC2E27D.6070101@redhat.com> (raw)
In-Reply-To: <878w1pkti4.fsf_-_@nemi.mork.no>
Em 23-10-2010 10:01, Bjørn Mork escreveu:
> Steven Toth <stoth@kernellabs.com> writes:
>> On 10/22/10 9:02 AM, Daniel Lee Kim wrote:
>>
>>> One more question, is there a place I can go to learn how to compile just the
>>> cx23885.ko module? I am not able to compile only that module and so I have to
>>> wait until it compiles all the modules. I apologize as this is my first time
>>> tweaking a driver module. I've searched all over the net but have not found
>>> anyone who wrote about this. Thanks,
>>
>> The wiki at linuxtv.org should contain everything you need for
>> compiling, modifying and submitting patches.
>
> It should, but it does not.
>
> Following the path from
> www.linuxtv.org => V4L-DVB Wiki => Developer Section => How to submit patches
> you end up at
> http://www.linuxtv.org/wiki/index.php/Development:_How_to_submit_patches
> which states
>
> 'For V4L-DVB driver modules and/or documentation, patches should be
> created against the master V4L-DVB mercurial tree; for instructions on
> obtaining and building these sources, see the "How to Obtain, Build and
> Install V4L-DVB Device Drivers" article.'
>
>
> and the "How to Obtain, Build and Install V4L-DVB Device Drivers"
> article contains more of the same outdated information, with its
> references to to 2.6.16 backwards compatibility and Mercurial.
>
> For a new developer coming from the outside, this is worse than not
> having any information at all. Anyone reading this list will know that
> the above quote is plain misleading. But as a new developer you have no
> way to know whether other information in the same page, or even the
> whole Wiki, is just as misleading. So you cannot trust any of it.
> Making the Wiki useless.
>
> Never write documentation you do not plan to keep updated. Delete
> outdated documentation if you don't have time/resources to update it.
> Misleading documentation is much, much worse than no documentation.
It is a wiki for a community effort. If you found it outdated, please help us
on keeping it uptodated.
Thanks,
Mauro
next prev parent reply other threads:[~2010-10-23 13:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <BLU0-SMTP179D180C75C88F1B693AA73A75A0@phx.gbl>
2010-10-19 21:27 ` cx23885 module Steven Toth
2010-10-20 16:19 ` Daniel Lee Kim
2010-10-20 20:58 ` Steven Toth
[not found] ` <SNT130-w25B4AAC1A5FC7F00372440A75E0@phx.gbl>
2010-10-22 13:06 ` Steven Toth
2010-10-23 12:01 ` linuxtv.org Wiki (was Re: cx23885 module) Bjørn Mork
2010-10-23 13:26 ` Mauro Carvalho Chehab [this message]
2010-10-24 11:25 ` linuxtv.org Wiki Bjørn Mork
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=4CC2E27D.6070101@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 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.