linux-kernel - Re: pull request: wireless-next-2.6 2009-09-23

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <20090923.162449.141768862.davem@davemloft.net>
Date:	Wed, 23 Sep 2009 16:24:49 -0700 (PDT)
From:	David Miller <davem@...emloft.net>
To:	linville@...driver.com
Cc:	linux-wireless@...r.kernel.org, netdev@...r.kernel.org,
	linux-kernel@...r.kernel.org
Subject: Re: pull request: wireless-next-2.6 2009-09-23

From: "John W. Linville" <linville@...driver.com>
Date: Wed, 23 Sep 2009 11:53:40 -0400

> Please accept this one last round of wireless bits for the merge window.
> They are fixes for the most part, and the teams involved are very eager
> to have these for the 2.6.32 cycle.  In particular, the b43 and ath9k
> teams have some late breakers -- yes, I have reminded them of the
> process, but they are quite insistent...
> 
> Please let me know if there are problems!

Pulled, but yes you guys need to stick to pure bug fixes at
this point, please.

Also, please put the branch name, even if it's simply 'master'
in your GIT pull urls you give me.

Thanks.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/