From: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>
To: Ivo van Doorn <ivdoorn@gmail.com>
Cc: Gertjan van Wingerde <gwingerde@gmail.com>,
users@rt2x00.serialmonkey.com, linux-wireless@vger.kernel.org
Subject: Re: [PATCH 2/2] rt2x00: Fix BUG on rt2800usb when trying to read eFuse EEPROM.
Date: Sun, 15 Nov 2009 14:09:38 +0100 [thread overview]
Message-ID: <200911151409.38444.bzolnier@gmail.com> (raw)
In-Reply-To: <200911142035.02611.IvDoorn@gmail.com>
On Saturday 14 November 2009 20:35:02 Ivo van Doorn wrote:
> On Saturday 14 November 2009, Gertjan van Wingerde wrote:
> > Current tree hits a BUG_ON in rt2x00_regbusy_read, because the eFuse EEPROM
> > reading code of rt2800lib uses the function without the csr_mutex locked.
> >
> > Fix this by locking the csr_mutex for the of the EEPROM reading cycly and
> > using the _lock variants of the register reading and writing functions.
> >
> > This also introcudes the register_read_lock function pointer in the
> > rt2800_ops structure.
> >
> > Signed-off-by: Gertjan van Wingerde <gwingerde@gmail.com>
>
> Acked-by: Ivo van Doorn <IvDoorn@gmail.com>
FWIW both patches are in rt2800 tree now.
Thanks.
--
Bartlomiej Zolnierkiewicz
next prev parent reply other threads:[~2009-11-15 13:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-14 19:20 [PATCH 0/2] rt2x00 fixes for rt2800 Gertjan van Wingerde
2009-11-14 19:20 ` [PATCH 1/2] rt2x00: Log RT/RF chipset information correctly Gertjan van Wingerde
2009-11-14 19:20 ` [PATCH 2/2] rt2x00: Fix BUG on rt2800usb when trying to read eFuse EEPROM Gertjan van Wingerde
2009-11-14 19:35 ` Ivo van Doorn
2009-11-15 13:09 ` Bartlomiej Zolnierkiewicz [this message]
2009-11-14 19:34 ` [PATCH 1/2] rt2x00: Log RT/RF chipset information correctly Ivo van Doorn
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=200911151409.38444.bzolnier@gmail.com \
--to=bzolnier@gmail.com \
--cc=gwingerde@gmail.com \
--cc=ivdoorn@gmail.com \
--cc=linux-wireless@vger.kernel.org \
--cc=users@rt2x00.serialmonkey.com \
/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;
as well as URLs for NNTP newsgroup(s).