From: Philipp Hortmann <philipp.g.hortmann@gmail.com>
To: Oliver Neukum <oneukum@suse.com>, "Theodore Y. Ts'o" <tytso@mit.edu>
Cc: linux-usb@vger.kernel.org, linux-doc@vger.kernel.org,
Greg KH <gregkh@linuxfoundation.org>
Subject: Re: proposal to delete the skeleton driver
Date: Sat, 11 Dec 2021 17:28:24 +0100 [thread overview]
Message-ID: <03204a1e-2423-5cd1-b116-9bae51e92000@gmail.com> (raw)
In-Reply-To: <9b33445d-7bf9-684a-bf53-f472bb928b96@suse.com>
On 12/8/21 12:13 PM, Oliver Neukum wrote:
>
> On 07.12.21 23:43, Theodore Y. Ts'o wrote:
>> 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.
> I will try to. It may come as a surprise but if we want to limit
> ourselves to drivers implementing a classical character device,
> the number of recent examples dwindles rapidly.
>
> And I think we should stick to such devices to give examples
> comprehensible and relevant to as many people as possible.
>
> Regards
> Oliver
>
>
I like drivers/usb/misc/usblcd.c as one simple example. An older version
of usb-skeleton was the template. It is using urbs only for writing.
Since no driver seems to cover everything we may need two examples of
maintained drivers as transfer performance and interrupt endpoints are
not relevant for usblcd.
Regards
Philipp
next prev parent reply other threads:[~2021-12-11 16:28 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
2021-12-08 11:13 ` Oliver Neukum
2021-12-11 16:28 ` Philipp Hortmann [this message]
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=03204a1e-2423-5cd1-b116-9bae51e92000@gmail.com \
--to=philipp.g.hortmann@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=oneukum@suse.com \
--cc=tytso@mit.edu \
/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