From: Jonathan Cameron <jic23@cam.ac.uk>
To: "linux-iio@vger.kernel.org" <linux-iio@vger.kernel.org>
Cc: Manuel Stahl <manuel.stahl@iis.fraunhofer.de>,
"Hennerich, Michael" <Michael.Hennerich@analog.com>,
Jon Brenner <jbrenner@taosinc.com>
Subject: Does anyone read device.txt etc?
Date: Thu, 15 Sep 2011 12:11:00 +0100 [thread overview]
Message-ID: <4E71DD44.7030407@cam.ac.uk> (raw)
Hi All,
I'm just wondering if some corners of our documentation are useful or not.
So straw poll. Has anyone ever read the stuff in
device.txt?
trigger.txt?
ring.txt?
I'm tempted to drop all 3 of these as pointless maintenance
overhead...
Obviously those I've cc'd are actually active developers and probably
don't look at any docs at all that often, so other lurkers / new developers
please do respond to this email!
A well commented dummy driver would be better for explaining these
things.
Thanks,
Jonathan
next reply other threads:[~2011-09-15 11:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-15 11:11 Jonathan Cameron [this message]
2011-09-16 4:52 ` Does anyone read device.txt etc? Jonathan Kunkee
2011-09-16 8:35 ` Jonathan Cameron
2011-09-16 9:29 ` Manuel Stahl
2011-09-16 9:41 ` Jonathan Cameron
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=4E71DD44.7030407@cam.ac.uk \
--to=jic23@cam.ac.uk \
--cc=Michael.Hennerich@analog.com \
--cc=jbrenner@taosinc.com \
--cc=linux-iio@vger.kernel.org \
--cc=manuel.stahl@iis.fraunhofer.de \
/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).