From: Larry Finger <Larry.Finger@lwfinger.net>
To: "Rafał Miłecki" <zajec5@gmail.com>
Cc: b43-dev <b43-dev@lists.infradead.org>,
wireless <linux-wireless@vger.kernel.org>
Subject: Re: Interesting development regarding b43 DMA ERROR
Date: Fri, 06 Aug 2010 12:37:36 -0500 [thread overview]
Message-ID: <4C5C4860.2030507@lwfinger.net> (raw)
In-Reply-To: <AANLkTi=-Jc9XjD-gqwtUyUnM768wvv3GzzwhJNtkwYKK@mail.gmail.com>
On 08/06/2010 11:31 AM, Rafał Miłecki wrote:
>
> Interesting. It means some patch that gone mainline fixed it and it
> was submitted using other tree than w-t, right?
>
> Would you care to bisect this?
It won't be fun as this is a 1.6 GHz Atom and a kernel build is quite slow. In
addition, this one has the relocated SPROM that requires patching to be able to
boot. In the interests of the community, I will do it.
Larry
next prev parent reply other threads:[~2010-08-06 17:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-05 21:06 Interesting development regarding b43 DMA ERROR Larry Finger
2010-08-06 16:31 ` Rafał Miłecki
2010-08-06 17:37 ` Larry Finger [this message]
2010-08-08 5:08 ` Kalle Valo
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=4C5C4860.2030507@lwfinger.net \
--to=larry.finger@lwfinger.net \
--cc=b43-dev@lists.infradead.org \
--cc=linux-wireless@vger.kernel.org \
--cc=zajec5@gmail.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).