netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Miller <davem-fT/PcQaiUtIeIZ0/mPfg9Q@public.gmane.org>
To: linville-2XuSBdqkA4R54TAoqtyWWQ@public.gmane.org
Cc: linux-wireless-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: pull request: wireless-next-2.6 2011-02-22
Date: Thu, 24 Feb 2011 22:43:44 -0800 (PST)	[thread overview]
Message-ID: <20110224.224344.104068328.davem@davemloft.net> (raw)
In-Reply-To: <20110222215229.GJ12153-2XuSBdqkA4R54TAoqtyWWQ@public.gmane.org>

From: "John W. Linville" <linville-2XuSBdqkA4R54TAoqtyWWQ@public.gmane.org>
Date: Tue, 22 Feb 2011 16:52:30 -0500

> Here is the latest batch of wireless bits intended for 2.6.39.  It seems
> I neglected to send a pull request last week, so this one is a bit big
> -- I apologize!
> 
> This includes a rather large batch of bluetooth bits by way of Gustavo.
> It looks like a variety of bits, including some code refactoring, some
> protocol support enhancements, some bugfixes, etc. -- nothing too
> unusual.
> 
> Other items of interest include a new driver from Realtek, some ssb
> support enhancements, and the usual sort of updates for mac80211 and a
> variety of drivers.  Also included is a wireless-2.6 pull to resolve
> some build breakage.
> 
> Please let me know if there are problems!

Pulled, thanks a lot John.
--
To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  parent reply	other threads:[~2011-02-25  6:43 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-22 21:52 pull request: wireless-next-2.6 2011-02-22 John W. Linville
     [not found] ` <20110222215229.GJ12153-2XuSBdqkA4R54TAoqtyWWQ@public.gmane.org>
2011-02-25  6:43   ` David Miller [this message]
     [not found]     ` <20110224.224344.104068328.davem-fT/PcQaiUtIeIZ0/mPfg9Q@public.gmane.org>
2011-02-25 19:15       ` David Miller
     [not found]         ` <20110225.111500.59674472.davem-fT/PcQaiUtIeIZ0/mPfg9Q@public.gmane.org>
2011-02-25 19:36           ` Gustavo F. Padovan
2011-02-26  1:36             ` Gustavo F. Padovan
2011-02-26  1:41               ` [PATCH] Bluetooth: Fix BT_L2CAP and BT_SCO in Kconfig Gustavo F. Padovan
2011-02-26 17:52                 ` Vitaly Wool
     [not found]                   ` <AANLkTimuyx4ixPq5BexRHozebVpjry2k-2xskqVf79g1-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2011-02-27 19:19                     ` Gustavo F. Padovan
     [not found]                 ` <1298684485-3081-1-git-send-email-padovan-Y3ZbgMPKUGA34EUeqzHoZw@public.gmane.org>
2011-03-03  5:54                   ` David Miller
     [not found]                     ` <20110302.215433.39198854.davem-fT/PcQaiUtIeIZ0/mPfg9Q@public.gmane.org>
2011-03-03 14:05                       ` John W. Linville
2011-02-25 19:48         ` pull request: wireless-next-2.6 2011-02-22 John W. Linville
2011-03-04  4:35   ` Shan Wei
     [not found]     ` <4D706C2E.40307-BthXqXjhjHXQFUHtdCDX3A@public.gmane.org>
2011-03-04 18:40       ` John W. Linville

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=20110224.224344.104068328.davem@davemloft.net \
    --to=davem-ft/pcqaiutieiz0/mpfg9q@public.gmane.org \
    --cc=linux-wireless-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=linville-2XuSBdqkA4R54TAoqtyWWQ@public.gmane.org \
    --cc=netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.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;
as well as URLs for NNTP newsgroup(s).