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

Message-Id: <200801231230.07734.mb@bu3sch.de>
Date:	Wed, 23 Jan 2008 12:30:07 +0100
From:	Michael Buesch <mb@...sch.de>
To:	Stefano Brivio <stefano.brivio@...imi.it>
Cc:	"John W. Linville" <linville@...driver.com>, davem@...emloft.net,
	netdev@...r.kernel.org, linux-wireless@...r.kernel.org
Subject: Re: pull request: wireless-2.6 'upstream' 2008-01-22

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
patches, they are completely untested. I usually compiletest them,
but that's it.
But in future I can also put a comment into the mailbody that
explains why to not apply it, yet.

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

-- 
Greetings Michael.
--
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