From: Jonathan Cameron <jic23@cam.ac.uk>
To: "linux-iio@vger.kernel.org" <linux-iio@vger.kernel.org>
Subject: iio-blue.git reorganization.
Date: Fri, 12 Aug 2011 17:35:09 +0100 [thread overview]
Message-ID: <4E45563D.4090204@cam.ac.uk> (raw)
This dev tree as I warned is not stable. It's more or less
a dump of my local working tree.
As such I hope no one minds the wholesale reorganization I've just
pushed out to kernel.org. Basically I've sorted patches
into fixes / cleanups1 / chan spec conversions / cleanups2 / controversial bits / other stuff.
fixes and cleanups1 have gone to Greg for now.
The controversial bits are:
* trigger rework to make removal safe.
* chrdevs merging into one.
* in_ out_ prefix on channnels.
* endian description addition.
* extend scan_mask and event codes to allow for more channels.
Comments on anything and everything welcome!
Jonathan
next reply other threads:[~2011-08-12 16:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-12 16:35 Jonathan Cameron [this message]
2011-08-12 17:18 ` iio-blue.git reorganization Jonathan Cameron
-- strict thread matches above, loose matches on Subject: below --
2011-08-25 16: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=4E45563D.4090204@cam.ac.uk \
--to=jic23@cam.ac.uk \
--cc=linux-iio@vger.kernel.org \
/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.