From: Larry Finger <Larry.Finger@lwfinger.net>
To: lina <lina.lastname@gmail.com>
Cc: linux-wireless@vger.kernel.org
Subject: Re: modprob b43 not work after hilibernate
Date: Mon, 09 Jan 2012 22:58:04 -0600 [thread overview]
Message-ID: <4F0BC55C.70509@lwfinger.net> (raw)
In-Reply-To: <4F0BBDBB.2060407@gmail.com>
On 01/09/2012 10:25 PM, lina wrote:
> On Tuesday 10,January,2012 01:19 AM, Larry Finger wrote:
>> On 01/08/2012 10:09 PM, lina wrote:
>>> On Monday 09,January,2012 05:44 AM, Rafał Miłecki wrote:
>>>> Does your kernel have
>>>> [PATCH] bcma: support for suspend and resume
>>>> applied?
>>>
>>> I don't know how to check, googled for a while, found some thread, but
>>> did not
>>> find the patch, is it in the kernel.org [patch] part, I thought the [full
>>> source] is already patched?
>>
>> The mainline kernel v3.2-3191-g36e9db2 has that patch.
>
> when I tried to open
> http://www.kernel.org/diff/diffview.cgi?file=/pub/linux/kernel/v3.0/patch-3.2.bz2
>
> diffview is looping on the cached resource:
> /home/httpd/cache/diffview/ZM/ZMxXxIlPZnZ9405Mc9XmGRWFlkM/index
>
> when I googled v3.2-3191-g36e9db2, it leads me to this thread only.
>
> sorry, I am confusing about how to get this patch and make it to patch.
>
> Thanks for your time,
Get the bleeding-edge version of compat-wireless. That will *always* get you the
latest set of patches.
Larry
next prev parent reply other threads:[~2012-01-10 4:58 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-08 14:40 modprob b43 not work after hilibernate lina
2012-01-08 16:05 ` Larry Finger
2012-01-08 16:18 ` lina
2012-01-08 21:44 ` Rafał Miłecki
2012-01-09 4:09 ` lina
2012-01-09 17:19 ` Larry Finger
2012-01-10 4:25 ` lina
2012-01-10 4:58 ` Larry Finger [this message]
2012-01-10 5:19 ` lina
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=4F0BC55C.70509@lwfinger.net \
--to=larry.finger@lwfinger.net \
--cc=lina.lastname@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.