From: Sebastian Siewior <bigeasy-hfZtesqFncYOwBW4kG4KsQ@public.gmane.org>
To: David Brownell <david-b-yBeKhBN/0LDR7s880joybQ@public.gmane.org>
Cc: spi-devel-general-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org,
Andrew Morton
<akpm-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@public.gmane.org>
Subject: Re: [PATCH] spi: fix the read path in spidev
Date: Wed, 02 Jul 2008 09:02:05 +0200 [thread overview]
Message-ID: <486B27ED.3000008@linutronix.de> (raw)
In-Reply-To: <200807011959.50695.david-b-yBeKhBN/0LDR7s880joybQ@public.gmane.org>
David Brownell wrote:
> On Tuesday 01 July 2008, Sebastian Siewior wrote:
>> This got broken by the recent "fix rmmod $spi_driver while spidev-user is active".
>> I tested the rmmod & write path but didn't check the read path. I am sorry.
>> The read logic changed and spidev_sync_read() + spidev_sync_write() do not return
>> zero on success anymore but the number of bytes that has been transfered over the
>> bus.
>> This patch changes the logic and copy_to_user() gets called again.
>
> Good catch ... did you observe this failure happening "in the wild"
> or was this a code-inspection kind of thing?
>
"in the wild". I've been testing HW testing after I rebased to -rc8 and
somehow I got no error but the receive buffer was empty....
Sebastian
-------------------------------------------------------------------------
Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW!
Studies have shown that voting for your favorite open source project,
along with a healthy diet, reduces your potential for chronic lameness
and boredom. Vote Now at http://www.sourceforge.net/community/cca08
prev parent reply other threads:[~2008-07-02 7:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-01 15:45 [PATCH] spi: fix the read path in spidev Sebastian Siewior
[not found] ` <20080701154504.GA26219-Hfxr4Dq0UpYb1SvskN2V4Q@public.gmane.org>
2008-07-01 20:07 ` Andrew Morton
2008-07-02 2:59 ` David Brownell
[not found] ` <200807011959.50695.david-b-yBeKhBN/0LDR7s880joybQ@public.gmane.org>
2008-07-02 7:02 ` Sebastian Siewior [this message]
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=486B27ED.3000008@linutronix.de \
--to=bigeasy-hfztesqfncyowbw4kg4ksq@public.gmane.org \
--cc=akpm-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@public.gmane.org \
--cc=david-b-yBeKhBN/0LDR7s880joybQ@public.gmane.org \
--cc=spi-devel-general-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.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.