From: Johannes Berg <johannes@sipsolutions.net>
To: Larry Finger <larry.finger@lwfinger.net>
Cc: Michael Buesch <mb@bu3sch.de>,
netdev@vger.kernel.org, Bcm43xx-dev@lists.berlios.de,
linux-wireless@vger.kernel.org
Subject: Re: [PATCH] bcm43xx: Fix for oops on resume
Date: Wed, 07 Feb 2007 14:54:50 +0100 [thread overview]
Message-ID: <1170856490.6798.40.camel@johannes.berg> (raw)
In-Reply-To: <45C9D930.5010307@lwfinger.net>
[-- Attachment #1: Type: text/plain, Size: 579 bytes --]
On Wed, 2007-02-07 at 07:50 -0600, Larry Finger wrote:
> Could you please apply this patch and tell me what gets printed after you resume, and whether you
> did a suspend to RAM or disk?
Not a bad idea. I can test suspend to ram as well as to disk, just got
both working again.
The kernel I'm running right now was built on my powermac so I can't do
it right away (otherwise I could've just recompiled the bcm43xx module)
but I'll do it later today or tomorrow.
Usually, to get my connection back after a suspend, I just have to set
the ssid again.
johannes
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 190 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: Johannes Berg <johannes-cdvu00un1VgdHxzADdlk8Q@public.gmane.org>
To: Larry Finger <larry.finger-tQ5ms3gMjBLk1uMJSBkQmQ@public.gmane.org>
Cc: Michael Buesch <mb-fseUSCV1ubazQB+pC5nmwQ@public.gmane.org>,
netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
Bcm43xx-dev-0fE9KPoRgkgATYTw5x5z8w@public.gmane.org,
linux-wireless-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH] bcm43xx: Fix for oops on resume
Date: Wed, 07 Feb 2007 14:54:50 +0100 [thread overview]
Message-ID: <1170856490.6798.40.camel@johannes.berg> (raw)
In-Reply-To: <45C9D930.5010307-tQ5ms3gMjBLk1uMJSBkQmQ@public.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 579 bytes --]
On Wed, 2007-02-07 at 07:50 -0600, Larry Finger wrote:
> Could you please apply this patch and tell me what gets printed after you resume, and whether you
> did a suspend to RAM or disk?
Not a bad idea. I can test suspend to ram as well as to disk, just got
both working again.
The kernel I'm running right now was built on my powermac so I can't do
it right away (otherwise I could've just recompiled the bcm43xx module)
but I'll do it later today or tomorrow.
Usually, to get my connection back after a suspend, I just have to set
the ssid again.
johannes
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 190 bytes --]
next prev parent reply other threads:[~2007-02-07 13:58 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-06 17:39 [PATCH] bcm43xx: Fix for oops on resume Larry Finger
2007-02-06 17:39 ` Larry Finger
2007-02-07 12:15 ` Johannes Berg
2007-02-07 12:15 ` Johannes Berg
2007-02-07 13:23 ` Larry Finger
2007-02-07 13:32 ` Johannes Berg
2007-02-07 13:32 ` Johannes Berg
2007-02-07 13:50 ` Larry Finger
2007-02-07 13:50 ` Larry Finger
2007-02-07 13:54 ` Johannes Berg [this message]
2007-02-07 13:54 ` Johannes Berg
2007-02-07 13:56 ` Johannes Berg
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=1170856490.6798.40.camel@johannes.berg \
--to=johannes@sipsolutions.net \
--cc=Bcm43xx-dev@lists.berlios.de \
--cc=larry.finger@lwfinger.net \
--cc=linux-wireless@vger.kernel.org \
--cc=mb@bu3sch.de \
--cc=netdev@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.