From: "René Rebe" <rene@exactcode.de>
To: Oliver Neukum <oliver@neukum.org>
Cc: linux-usb-devel@lists.sourceforge.net,
Andrew Morton <akpm@osdl.org>,
linux-kernel@vger.kernel.org
Subject: Re: [linux-usb-devel] Re: [PATCH] Adaptec USBXchange and USB2Xchange support
Date: Mon, 30 Jan 2006 16:36:15 +0100 [thread overview]
Message-ID: <200601301636.15258.rene@exactcode.de> (raw)
In-Reply-To: <200601301622.19998.oliver@neukum.org>
Hi,
On Monday 30 January 2006 16:22, Oliver Neukum wrote:
> Am Montag, 30. Januar 2006 14:22 schrieb René Rebe:
> > + /* Stop CPU */
> > + err = usbxchange_set_reset(dev, cpureg, 1);
> > + err = usbxchange_set_reset(dev, cpureg, 1);
> > + if (err < 0) {
> > + printk(KERN_ERR "%s - error stopping dongle CPU: error = %d\n",
> > + __FUNCTION__, err);
> > + return err;
> > + }
>
> [..]
>
> > + /* De-assert reset (let the CPU run) */
> > + err = usbxchange_set_reset(dev, cpureg, 1);
> > + err = usbxchange_set_reset(dev, cpureg, 0);
> > + if (err < 0) {
> > + printk(KERN_ERR "%s - error resetting dongle CPU: error = %d\n",
> > + __FUNCTION__, err);
> > + return err;
> > + }
>
> Do you really want to ignore errors the first usbxchange_set_reset()s return?
It is not really likely that the first one fails and the second succeeds. But yes,
I could add an if (err == 0) before the 2nd send and skip it when the first already
failed.
I can resent with more suggestions accumulated.
Yours,
--
René Rebe - Rubensstr. 64 - 12157 Berlin (Europe / Germany)
http://www.exactcode.de | http://www.t2-project.org
+49 (0)30 255 897 45
next prev parent reply other threads:[~2006-01-30 15:36 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-13 20:53 [PATCH] Adaptec USBXchange and USB2Xchange support René Rebe
2005-09-14 10:18 ` Andrew Morton
2006-01-30 13:22 ` René Rebe
2006-01-30 13:33 ` René Rebe
[not found] ` <200601301622.19998.oliver@neukum.org>
2006-01-30 15:36 ` René Rebe [this message]
2006-01-30 18:04 ` [linux-usb-devel] " René Rebe
2006-01-30 21:38 ` Matthew Dharm
2006-01-30 21:40 ` Matthew Dharm
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=200601301636.15258.rene@exactcode.de \
--to=rene@exactcode.de \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb-devel@lists.sourceforge.net \
--cc=oliver@neukum.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