From: Kalle Valo <kvalo@qca.qualcomm.com>
To: gregkh@suse.de
Cc: devel@linuxdriverproject.org, linux-wireless@vger.kernel.org
Subject: [PATCH 0/2] ath6kl: fix suspend/resume crashes for 3.0
Date: Mon, 13 Jun 2011 11:53:50 +0300 [thread overview]
Message-ID: <20110613085118.15065.16173.stgit@localhost6.localdomain6> (raw)
Hi Greg,
here are two fixes suspend/resume crash fixes for 3.0. This is v2 based
on the feedback from Dan Carpenter.
---
Kalle Valo (2):
ath6kl: fix crash when interface is closed but scan is ongoing
ath6kl: cache firmware
drivers/staging/ath6kl/os/linux/ar6000_drv.c | 49 ++++++++++++++------
drivers/staging/ath6kl/os/linux/cfg80211.c | 31 +++++++------
.../staging/ath6kl/os/linux/include/ar6000_drv.h | 9 ++++
3 files changed, 61 insertions(+), 28 deletions(-)
next reply other threads:[~2011-06-13 8:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-13 8:53 Kalle Valo [this message]
2011-06-13 8:54 ` [PATCH 1/2] ath6kl: fix crash when interface is closed but scan is ongoing Kalle Valo
2011-06-13 8:54 ` [PATCH 2/2] ath6kl: cache firmware 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=20110613085118.15065.16173.stgit@localhost6.localdomain6 \
--to=kvalo@qca.qualcomm.com \
--cc=devel@linuxdriverproject.org \
--cc=gregkh@suse.de \
--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