netdev - Re: pull request: wireless-2.6 'upstream' 2008-01-22

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] [day] [month] [year] [list]

Message-ID: <20080123124639.GB3157@tuxdriver.com>
Date:	Wed, 23 Jan 2008 07:46:39 -0500
From:	"John W. Linville" <linville@...driver.com>
To:	Michael Buesch <mb@...sch.de>
Cc:	Stefano Brivio <stefano.brivio@...imi.it>, davem@...emloft.net,
	netdev@...r.kernel.org, linux-wireless@...r.kernel.org
Subject: Re: pull request: wireless-2.6 'upstream' 2008-01-22

On Wed, Jan 23, 2008 at 12:30:07PM +0100, Michael Buesch wrote:
> On Wednesday 23 January 2008 12:15:51 Stefano Brivio wrote:
> > On Tue, 22 Jan 2008 20:45:21 -0500
> > "John W. Linville" <linville@...driver.com> wrote:
> > 
> > >       b43legacy: Remove the PHY spinlock
> > 
> > I hope you tested this. I still haven't been able to (I received the
> > needed hardware yesterday), and Michael said that the patch has been
> > compile-tested only.
> 
> John, if we use subject lines such as:
> 
> [PATCH RFT] foobar: bizbaz
> 
> That means the patch is _not_ submitted for inclusion, yet.
> The RFT means Request-For-Testing. Ususally, if I send out such

Thanks, I'm well aware.

Larry said he tested it, two weeks ago.  No one contradicted it.
And time is short for new development for 2.6.25 -- but there is
plenty of time for fixes. :-)

> For this particular patch, please leave it in now. I'm pretty
> sure it is correct. So actual testing will be done upstream now. ;)

Exactly.

John
-- 
John W. Linville
linville@...driver.com
--
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