From: Oliver Neukum <oneukum@suse.com>
To: linux-usb@vger.kernel.org
Cc: linux-doc@vger.kernel.org,
Philipp Hortmann <philipp.g.hortmann@gmail.com>
Subject: proposal to delete the skeleton driver
Date: Tue, 7 Dec 2021 11:16:37 +0100 [thread overview]
Message-ID: <df5bb0a6-e5f5-e062-5c02-e1de612058e2@suse.com> (raw)
Hi,
it seems to me that the method of maintaining an example driver
does not work because it will inevitably be
* untested
* out of date
Thus our documentation would be improved by replacing its examples
with code from drivers for real hardware. Such code wouldn't be pretty
or written for text books, but it would be tested.
I could do it this week in a first proposal. But I don't want to start
if somebody feels that the skeleton driver absolutely has to stay.
Regards
Oliver
next reply other threads:[~2021-12-07 10:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-07 10:16 Oliver Neukum [this message]
2021-12-07 10:24 ` proposal to delete the skeleton driver Greg KH
2021-12-07 22:43 ` Theodore Y. Ts'o
2021-12-08 11:13 ` Oliver Neukum
2021-12-11 16:28 ` Philipp Hortmann
2021-12-08 18:13 ` Philipp Hortmann
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=df5bb0a6-e5f5-e062-5c02-e1de612058e2@suse.com \
--to=oneukum@suse.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=philipp.g.hortmann@gmail.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;
as well as URLs for NNTP newsgroup(s).