From: Pavel Roskin <proski@gnu.org>
To: Golden <goldenstranger@yahoo.com>
Cc: linux-wireless@vger.kernel.org
Subject: Re: firmware_loading_store: vmap() failed, broken firmware with kernles .27 - .30
Date: Thu, 01 Apr 2010 21:53:43 -0400 [thread overview]
Message-ID: <1270173223.9735.6.camel@mj> (raw)
In-Reply-To: <365137.1684.qm@web56804.mail.re3.yahoo.com>
On Wed, 2010-03-31 at 14:56 -0700, Golden wrote:
> This appears to be an important bug fix for a variety of users with
> older kernels. Can you prepare proper patch for this and did you have
> a chance to test if these amendments cause trouble with newer
> kernels?
I realize that it's an important issue, but I don't have time to look
for a solution right now. I did my part by confirming the problem on an
2.6.28.10 kernel. I don't see it on other kernels, but since it's a
race condition, I cannot say definitely that the same condition cannot
happen on another system running a newer kernel.
--
Regards,
Pavel Roskin
next prev parent reply other threads:[~2010-04-02 1:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-25 16:20 firmware_loading_store: vmap() failed, broken firmware with kernles .27 - .30 Golden
2010-03-27 12:22 ` Golden
2010-03-31 3:15 ` Pavel Roskin
2010-03-31 21:56 ` Golden
2010-04-02 1:53 ` Pavel Roskin [this message]
-- strict thread matches above, loose matches on Subject: below --
2010-04-02 6:42 Golden
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=1270173223.9735.6.camel@mj \
--to=proski@gnu.org \
--cc=goldenstranger@yahoo.com \
--cc=linux-wireless@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;
as well as URLs for NNTP newsgroup(s).