netdev - Re: Please pull 'rt2x00' branch of wireless-2.6

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]

Date:	Wed, 19 Sep 2007 20:36:59 +0200
From:	Michael Buesch <mb@...sch.de>
To:	Ivo van Doorn <ivdoorn@...il.com>
Cc:	David Miller <davem@...emloft.net>, linville@...driver.com,
	jeff@...zik.org, netdev@...r.kernel.org,
	linux-wireless@...r.kernel.org
Subject: Re: Please pull 'rt2x00' branch of wireless-2.6

On Wednesday 19 September 2007 20:47:59 Ivo van Doorn wrote:
> On Wednesday 19 September 2007, David Miller wrote:
> > From: Ivo van Doorn <ivdoorn@...il.com>
> > Date: Wed, 19 Sep 2007 20:31:19 +0200
> > 
> > > Because I am indeed not really happy with this early merge, but I'll do my
> > > best to resolve the last outstanding bugs as soon as possible.
> > 
> > Relax :-)
> 
> :)
> 
> > A merge upstream doesn't mean "bug free", it means "significantly
> > better than no driver at all" and that is undoubtedly the case
> > here.
> 
> Well I am happy rt2x00 is being considered good enough for upstream already,
> but I have the habbit of wanting things bug-free before pushing it further upstream.
> 
> Well most users are happy with current rt2x00 version anyway,
> so the remaining issues probably aren't that big anyway. (Except for the 2 panics,
> which should be resolved soon anyway) ;)

Well, you have nothing to lose, basically.
It's impossible for you to create a regression.
So everything is fine, even if it's buggy and doesn't
work at all. ;)

-- 
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