From: Jonathan Cameron <jic23@cam.ac.uk>
To: "linux-iio@vger.kernel.org" <linux-iio@vger.kernel.org>
Subject: iio-blue.git - contents.
Date: Mon, 25 Jul 2011 14:42:38 +0100 [thread overview]
Message-ID: <4E2D72CE.7040508@cam.ac.uk> (raw)
git://git.kernel.org/pub/scm/linux/kernel/git/jic23/iio-blue.git
1: Misc fixes
2: Last removal of dev_data usage and removal of field (long since reviewed)
3: Trigger registration and removal cleanup (already posted).
4: General cleanup
5: chrdev combining
6: abi rework to have in and out prefixes for all channel attributes.
7: Scaling issue related changes to allow for lots of channels.
8: Misc fixes and cleanups.
Please do note the tree will be rebased.
As ever all reviews welcome!
Thanks,
Jonathan
reply other threads:[~2011-07-25 13:42 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=4E2D72CE.7040508@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox