From: Greg KH <gregkh@linuxfoundation.org>
To: "Bjørn Mork" <bjorn@mork.no>
Cc: Constantine Shulyupin <const@MakeLinux.com>,
linux-kernel@vger.kernel.org, celinux-dev@lists.celinuxforum.org,
Ryan Mallon <rmallon@gmail.com>, Tim Bird <tim.bird@am.sony.com>,
Baruch Siach <baruch@tkos.co.il>,
Thomas Petazzoni <thomas.petazzoni@free-electrons.com>,
Peter Korsgaard <jacmet@sunsite.dk>,
Ezequiel Garcia <elezegarcia@gmail.com>,
Selim TEMUR <selimtemur@gmail.com>,
Jean-Christophe PLAGNIOL-VILLARD <plagnioj@jcrosoft.com>
Subject: Re: [PATCH v2] LDT - Linux Driver Template
Date: Fri, 16 Nov 2012 04:08:36 -0800 [thread overview]
Message-ID: <20121116120836.GB13498@kroah.com> (raw)
In-Reply-To: <87zk2hubh1.fsf@nemi.mork.no>
On Fri, Nov 16, 2012 at 10:46:18AM +0100, Bjørn Mork wrote:
> Greg KH <gregkh@linuxfoundation.org> writes:
>
> > Normally you just start with a
> > driver for a device like the one you need to write and modify it from
> > there.
>
> Yes.
>
> Even if the template driver is fixed up to be the most beautiful driver
> ever made, it will still always be made for non-existing hardware. This
> causes two major problems:
> - the driver will not be tested, so it will have bugs
> - the driver will not be used by anyone, so it will not be maintained
> (remember that it is initially perfect, so there is no reason to
> change it)
>
> May I suggest another approach? How about selecting a set of existing
> drivers which are suitable as templates, and put all this effort into
> making those drivers *the* perfect examples instead? Start submitting
> cleanup patches for the selected drivers until everyone is satisfied and
> then document them as starting points for anyone wanting to write a
> similar driver.
I agree, this is a much better idea. Basing any new driver on a
known-working driver is highly preferable.
thanks,
greg k-h
next prev parent reply other threads:[~2012-11-16 12:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1353007337-12791-1-git-send-email-const@MakeLinux.com>
2012-11-15 22:40 ` [PATCH v2] LDT - Linux Driver Template Greg KH
2012-11-16 9:46 ` Bjørn Mork
2012-11-16 10:27 ` Constantine Shulyupin
2012-11-16 12:08 ` Greg KH [this message]
2012-11-17 12:52 ` Constantine Shulyupin
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=20121116120836.GB13498@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=baruch@tkos.co.il \
--cc=bjorn@mork.no \
--cc=celinux-dev@lists.celinuxforum.org \
--cc=const@MakeLinux.com \
--cc=elezegarcia@gmail.com \
--cc=jacmet@sunsite.dk \
--cc=linux-kernel@vger.kernel.org \
--cc=plagnioj@jcrosoft.com \
--cc=rmallon@gmail.com \
--cc=selimtemur@gmail.com \
--cc=thomas.petazzoni@free-electrons.com \
--cc=tim.bird@am.sony.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.