From: David Miller <davem@davemloft.net>
To: linville@tuxdriver.com
Cc: linux-wireless@vger.kernel.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: pull request: wireless 2013-01-04
Date: Fri, 04 Jan 2013 13:24:26 -0800 (PST) [thread overview]
Message-ID: <20130104.132426.2174792167438869648.davem@davemloft.net> (raw)
In-Reply-To: <20130104205343.GB21871@tuxdriver.com>
From: "John W. Linville" <linville@tuxdriver.com>
Date: Fri, 4 Jan 2013 15:53:43 -0500
> Arend "fixes" a copyright notice in brcmsmac -- seems harmless.
>
> Christian Lamparter adds a device ID to p54usb, and changes the
> interface combinations reported by carl9170 in order to get it
> working again.
>
> Geert Uytterhoeven gives us a pair of fixes for Kconfig warnings
> about bcma and ssb.
>
> Hante Meuleman fixes some IE parsing to get AP mode working with
> WPA2 security.
>
> Jesper Juhl fixes a urb leak in rtlwifi.
>
> Jussi Kivilinna fixes some mis-usage of usb_alloc_coherent in rtlwifi,
> avoiding a BUG on ARM.
>
> Larry Finger provides a handful of rtlwifi fixes to avoid some log
> SPAM due to not checking the return of pci_map_single.
>
> Niels Ole Salscheider changes a usleep_range in brcmsmac to use udelay
> instead, avoiding a "BUG: scheduling while atomic".
>
> Rafał Miłecki fixes an ID for a serial flash in the bcma code.
>
> Sujith Manoharan provides a pair of ath9k fixes, one for a compilation
> break and one to correct some gain-related initvals.
>
> Tomasz Guszkowski adds a device ID to p54usb.
>
> Vladimir Kondratiev fixes a Kconfig problem which cause ath9k_htc
> not to build properly.
>
> Please let me know if there are problems!
Pulled, thanks John.
prev parent reply other threads:[~2013-01-04 21:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-04 20:53 pull request: wireless 2013-01-04 John W. Linville
2013-01-04 21:24 ` David Miller [this message]
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=20130104.132426.2174792167438869648.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--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 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).