linux-doc.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Theodore Y. Ts'o" <tytso@mit.edu>
To: Oliver Neukum <oneukum@suse.com>
Cc: linux-usb@vger.kernel.org, linux-doc@vger.kernel.org,
	Philipp Hortmann <philipp.g.hortmann@gmail.com>
Subject: Re: proposal to delete the skeleton driver
Date: Tue, 7 Dec 2021 17:43:58 -0500	[thread overview]
Message-ID: <Ya/jrm59Ai226JtE@mit.edu> (raw)
In-Reply-To: <df5bb0a6-e5f5-e062-5c02-e1de612058e2@suse.com>

On Tue, Dec 07, 2021 at 11:16:37AM +0100, Oliver Neukum wrote:
> 
> 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.

In addition to your idea, I wonder if we could point people at some
simple "real world" drivers that people could look at which are (a)
simple, and (b) relatively clean and free of anti-patterns that we
don't want driver authors to copy pasta into their drivers.

Sort of like how we have the "minix" and "ext2" file systems as
examples that we will sometimes point people to who want to understand
how to do their own new file systems.

       	  	    	     - Ted

  parent reply	other threads:[~2021-12-07 22:44 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-07 10:16 proposal to delete the skeleton driver Oliver Neukum
2021-12-07 10:24 ` Greg KH
2021-12-07 22:43 ` Theodore Y. Ts'o [this message]
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=Ya/jrm59Ai226JtE@mit.edu \
    --to=tytso@mit.edu \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=oneukum@suse.com \
    --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).