From: Holger Schurig <hs4233@mail.mn-solutions.de>
To: Andreas Schwab <schwab@suse.de>
Cc: libertas-dev@lists.infradead.org, Dan Williams <dcbw@redhat.com>,
linux-wireless@vger.kernel.org,
"John W. Linville" <linville@tuxdriver.com>
Subject: Re: [PATH] libertas: speeds up downloading of CF firmware
Date: Fri, 23 May 2008 13:26:31 +0200 [thread overview]
Message-ID: <200805231326.31570.hs4233@mail.mn-solutions.de> (raw)
In-Reply-To: <jeve15b72o.fsf@sykes.suse.de>
> That changes the return value. Although it doesn't matter
> since all callers only check for < 0, it should perhaps be
> changed to return 0 here to avoid confusion.
You're right, the function returns now different things. But no
caller cares for the different return value, therefore the code
is correct as it is.
I actually used the return value to find out how many loops
usually are needed to program, and found that I wait way to long
in usleep() function.
next prev parent reply other threads:[~2008-05-23 11:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-23 8:18 [PATH] libertas: speeds up downloading of CF firmware Holger Schurig
2008-05-23 11:20 ` Andreas Schwab
2008-05-23 11:26 ` Holger Schurig [this message]
2008-05-23 13:41 ` Dan Williams
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=200805231326.31570.hs4233@mail.mn-solutions.de \
--to=hs4233@mail.mn-solutions.de \
--cc=dcbw@redhat.com \
--cc=libertas-dev@lists.infradead.org \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=schwab@suse.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