From: Jonathan Cameron <jic23@cam.ac.uk>
To: Manuel Stahl <manuel.stahl@iis.fraunhofer.de>
Cc: "linux-iio@vger.kernel.org" <linux-iio@vger.kernel.org>
Subject: Re: [PATCH 2/2] staging:iio move scan_elements into ring buffer
Date: Mon, 30 Aug 2010 17:48:52 +0100 [thread overview]
Message-ID: <4C7BE0F4.30004@cam.ac.uk> (raw)
In-Reply-To: <4C7BDCFF.7070305@iis.fraunhofer.de>
On 08/30/10 17:31, Manuel Stahl wrote:
> Am 30.08.2010 18:12, schrieb Jonathan Cameron:
>> On 08/30/10 14:37, Manuel Stahl wrote:
>>> Am 30.08.2010 14:58, schrieb Jonathan Cameron:
>>>> On 08/30/10 11:55, Manuel Stahl wrote:
>>>>> Signed-off-by: Manuel Stahl<manuel.stahl@iis.fraunhofer.de>
>>>>
>>>> On more complex patches like this, could you verify which devices
>>>> you have tested against? Given the nature of that patch it
>>>> probably doesn't matter that much, but it's nice to save people
>>>> from wondering if they need to test on devices you have already
>>>> tried it with.
>>>
>>> I have an sca3000 and an adis16405 to test with. The patch was made against v26.36-rc2 and compiled fine for all drivers in staging.
>> Glad you have an sca3000. My test board is currently broken so I've just
>> been crossing my fingers that I hadn't broken the driver with recent code
>> changes! Have you had any problems with the adis16405? I'm currently getting
>> seg faults with an adis16350 that I can't seem to track down. I'm waiting
>> for Barry to answer a few queries on that one...
>
> I know where the segfaults come from: iio_scan_el_show, etc.
> I forgot to cast to a buffer instead of a iio_dev.
Nope, the problem was pre todays patches, though obviously please fix
that one ;) That kit is at home so I'll give it another poke this evening.
>
> For sca3000 I have some problems with the ring buffer. The event doesn't get triggered.
Guess I should fix my board and take another look at that driver.
Jonathan
next prev parent reply other threads:[~2010-08-30 16:44 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-27 8:57 [IIO] Cleanup userspace Manuel Stahl
[not found] ` <4C77AC01.3090204@cam.ac.uk>
[not found] ` <4C77B68B.4060805@iis.fraunhofer.de>
2010-08-27 14:24 ` Jonathan Cameron
2010-08-27 14:31 ` Manuel Stahl
2010-08-27 15:09 ` Jonathan Cameron
2010-08-30 10:55 ` [PATCH 1/2] staging:iio rename ring attributes Manuel Stahl
2010-08-30 12:28 ` Jonathan Cameron
2010-08-30 10:55 ` [PATCH 2/2] staging:iio move scan_elements into ring buffer Manuel Stahl
2010-08-30 12:58 ` Jonathan Cameron
2010-08-30 13:37 ` Manuel Stahl
2010-08-30 14:09 ` Jonathan Cameron
[not found] ` <4C7BD886.3060109@cam.ac.uk>
2010-08-30 16:31 ` Manuel Stahl
2010-08-30 16:48 ` Jonathan Cameron [this message]
2010-08-30 14:03 ` [PATCH 1/3] staging:iio update documentation Manuel Stahl
2010-08-30 14:23 ` Jonathan Cameron
2010-08-30 14:24 ` Manuel Stahl
2010-08-30 14:49 ` Jonathan Cameron
2010-08-30 14:03 ` [PATCH 2/3] staging:iio sync drivers with current ABI Manuel Stahl
2010-08-30 14:44 ` Jonathan Cameron
2010-08-30 15:00 ` Manuel Stahl
2010-08-30 15:42 ` Jonathan Cameron
2010-08-30 15:48 ` Manuel Stahl
2010-08-30 16:07 ` Jonathan Cameron
2010-08-30 16:28 ` Manuel Stahl
2010-08-30 16:43 ` Jonathan Cameron
2010-08-30 14:03 ` [PATCH 3/3] staging:iio:hmc5843 change ABI to comply with documentation Manuel Stahl
2010-08-30 14:58 ` Jonathan Cameron
2010-08-31 12:16 ` Datta, Shubhrajyoti
2010-09-04 17:26 ` [IIO] Cleanup userspace 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=4C7BE0F4.30004@cam.ac.uk \
--to=jic23@cam.ac.uk \
--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