From: Jonathan Cameron <jic23@cam.ac.uk>
To: "linux-iio@vger.kernel.org" <linux-iio@vger.kernel.org>
Subject: iio-abi-new tree scrapped
Date: Wed, 05 May 2010 12:22:19 +0100 [thread overview]
Message-ID: <4BE154EB.9070701@cam.ac.uk> (raw)
Dear All,
Given the whole contents of the iio-abi-new tree
is now in staging-next and Greg KH also fixed a lot
of sparse warnings and one hidious bug with wrong parameter
ordering in a kzalloc in max1363 *tries not to look too embarassed*.
I have just removed the iio-abi-new tree from kernel.org.
I'll get into the habit of running a recent version of sparse
on my patch sets. One lives and learns. Much thanks is due
to Greg for the fix ups!
Thanks,
Jonathan
reply other threads:[~2010-05-05 11:19 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=4BE154EB.9070701@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