netdev - Re: pull request: wireless-next-2.6 2009-06-10

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 for Android: free password hash cracker in your pocket

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

Message-Id: <20090610.234424.69074010.davem@davemloft.net>
Date:	Wed, 10 Jun 2009 23:44:24 -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-06-10

From: "John W. Linville" <linville@...driver.com>
Date: Wed, 10 Jun 2009 14:56:39 -0400

> Despite my previous optimistic prediction, I need to ask for one more
> 2.6.31 pull before/during the merge window... :-)
> 
> This one actually does have a number of bug fixes embedded within, as
> well as some further fleshing-out and usage of the new rfkill
> infrastructure changes that are already queued for 2.6.31.  The other
> bits are more minor, but they have already spent at least a few days in
> -next and I believe they are safe for 2.6.31.

Pulled, I'll push out after some build verifications.

> P.S.  For some reason (probably the 2.6.30 release) the public push on
> kernel.org seems to be taking a lot longer than usual.  So you probably
> want to ensure that the wireless-next-2.6 head matches 2f0accc13520 or
> just pull using ssh (or direct file access).

I verified this, but you can sidestep this entire problem by simply
giving me master.kernel.org SSH based URLs to pull from. :-)

--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html