From: David Gibson <hermes@gibson.dropbear.id.au>
To: Stephen Evanchik <evanchsa@clarkson.edu>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2.5.54] UPDATE hermes: serialization fixes
Date: Sat, 4 Jan 2003 16:38:01 +1100 [thread overview]
Message-ID: <20030104053801.GF20016@zax.zax> (raw)
In-Reply-To: <200301031550.55590.evanchsa@clarkson.edu>
On Fri, Jan 03, 2003 at 03:50:55PM -0500, Stephen Evanchik wrote:
> This fixes "Error -110 writing Tx descriptor to BAP" bug as referenced in David Gibson's README.
>
> As per a suggestion, I've moved the spin_lock/unlock to hermes_bap_seek(). I'm currently running with
> this module and it's working nicely.
>
> As always, any comments are appreciated. Patches can be always downloaded from here:
I don't see how this can make any difference on the 0.13 and later
versions of the driver (which is in 2.5), since all BAP operations are
already serialized by the lock in the orinoco_private structure.
--
David Gibson | For every complex problem there is a
david@gibson.dropbear.id.au | solution which is simple, neat and
| wrong.
http://www.ozlabs.org/people/dgibson
prev parent reply other threads:[~2003-01-04 5:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-03 20:50 [PATCH 2.5.54] UPDATE hermes: serialization fixes Stephen Evanchik
2003-01-04 5:38 ` David Gibson [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=20030104053801.GF20016@zax.zax \
--to=hermes@gibson.dropbear.id.au \
--cc=evanchsa@clarkson.edu \
--cc=linux-kernel@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