From: Hauke Mehrtens <hauke@hauke-m.de>
To: mcgrof@gmail.com
Cc: linux-wireless@vger.kernel.org, Hauke Mehrtens <hauke@hauke-m.de>
Subject: [PATCH 0/2] compat-wireless-stable-2.6.37
Date: Sun, 9 Jan 2011 16:06:19 +0100 [thread overview]
Message-ID: <1294585581-9991-1-git-send-email-hauke@hauke-m.de> (raw)
These two patches should be backported form compat-wireless based on
linux-next to the stable version 2.6.37 as they are fixing some build
issues with some kernel version.
Hauke Mehrtens (1):
compat-wireless: backport power api in atl1c
Luis R. Rodriguez (1):
compat-wireless: remove 28-pm-qos-params.patch
patches/11-dev-pm-ops.patch | 50 +++++++++++++++++
patches/28-pm-qos-params.patch | 118 ----------------------------------------
2 files changed, 50 insertions(+), 118 deletions(-)
delete mode 100644 patches/28-pm-qos-params.patch
next reply other threads:[~2011-01-09 15:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-09 15:06 Hauke Mehrtens [this message]
2011-01-09 15:06 ` [PATCH 1/2] compat-wireless: remove 28-pm-qos-params.patch Hauke Mehrtens
2011-01-09 15:06 ` [PATCH 2/2] compat-wireless: backport power api in atl1c Hauke Mehrtens
2011-01-13 0:55 ` [PATCH 0/2] compat-wireless-stable-2.6.37 Luis R. Rodriguez
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=1294585581-9991-1-git-send-email-hauke@hauke-m.de \
--to=hauke@hauke-m.de \
--cc=linux-wireless@vger.kernel.org \
--cc=mcgrof@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).