linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: John Linville <linville@tuxdriver.com>
Cc: linux-wireless@vger.kernel.org
Subject: [PATCH 0/6] the entire rfkill patchset
Date: Tue, 02 Jun 2009 13:01:36 +0200	[thread overview]
Message-ID: <20090602110136.631660156@sipsolutions.net> (raw)

I'm getting confused by multiple patch versions, so
let me resend this to make sure you have the latest
versions of all patches.

johannes


             reply	other threads:[~2009-06-02 11:12 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-02 11:01 Johannes Berg [this message]
2009-06-02 11:01 ` [PATCH 1/6 v11] rfkill: rewrite Johannes Berg
2009-06-02 11:01 ` [PATCH 2/6 v6] rfkill: create useful userspace interface Johannes Berg
2009-06-02 11:01 ` [PATCH 3/6] cfg80211: move txpower wext from mac80211 Johannes Berg
2009-06-02 11:01 ` [PATCH 4/6] rfkill: add function to query state Johannes Berg
2009-06-02 11:01 ` [PATCH 5/6 v3] cfg80211: add rfkill support Johannes Berg
2009-06-02 11:01 ` [PATCH 6/6 v2] iwm: port to new cfg80211 rfkill 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=20090602110136.631660156@sipsolutions.net \
    --to=johannes@sipsolutions.net \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.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).