Linux IIO development
 help / color / mirror / Atom feed
From: Jonathan Cameron <jic23@cam.ac.uk>
To: Jonathan Cameron <jic23@cam.ac.uk>
Cc: linux-iio@vger.kernel.org
Subject: Re: [PATCH 1/3] staging:iio: remove broken support for multiple event interfaces.
Date: Fri, 29 Jul 2011 18:18:03 +0100	[thread overview]
Message-ID: <4E32EB4B.2020500@cam.ac.uk> (raw)
In-Reply-To: <4E32EB21.2010000@cam.ac.uk>

On 07/29/11 18:17, Jonathan Cameron wrote:
> On 07/25/11 14:35, Jonathan Cameron wrote:
>> We don't have a use case for these.  Two drivers appeared to use them
>> but both report all events on the first.
> Silly bug in here as well.  It subtracts one from an unsigned before doing a
> comparison.  Result is that for some devices, the masklength will end up as 0
> and hence all sorts of fun will occur. Sorry about that, will be fixed in the
> git tree in a few mins.
Where this applies to the next patch not this one. Oops.

  reply	other threads:[~2011-07-29 17:18 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-25 13:35 [PATCH 0/3] blue part 7: IIO Allow for more channels Jonathan Cameron
2011-07-25 13:35 ` [PATCH 1/3] staging:iio: remove broken support for multiple event interfaces Jonathan Cameron
2011-07-26  9:04   ` Hennerich, Michael
2011-07-29 17:17   ` Jonathan Cameron
2011-07-29 17:18     ` Jonathan Cameron [this message]
2011-07-25 13:35 ` [PATCH 2/3] staging:iio: Switch the channel masks to bitmaps so as to allow for more channels Jonathan Cameron
2011-08-18 14:15   ` Jonathan Cameron
2011-07-25 13:35 ` [PATCH 3/3] staging:iio:events - new 64 bit code structure and push out drivers 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=4E32EB4B.2020500@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