linux-kernel - Re: wireless abi breakage (was Re: 2.6.18-git9 wireless fixes break ipw2200 association to AP with WPA)

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: <20061005124036.GA4624@ucw.cz>
Date:	Thu, 5 Oct 2006 12:40:37 +0000
From:	Pavel Machek <pavel@....cz>
To:	Jean Tourrilhes <jt@....hp.com>
Cc:	Alessandro Suardi <alessandro.suardi@...il.com>,
	"John W. Linville" <linville@...driver.com>,
	Linux Kernel <linux-kernel@...r.kernel.org>,
	Andrew Morton <akpm@...l.org>
Subject: Re: wireless abi breakage (was Re: 2.6.18-git9 wireless fixes break ipw2200 association to AP with WPA)

Hi!

> > > 	That's exactly the point of this warning (some distro like to
> > > kill it), I think it spells pretty clearly what's wrong. Don't say I
> > > did not warn you...
> > 
> > Well... we are trying to have stable abi here. Breaking older wireless
> > tools randomly is *not* okay in the middle of stable series.
> 
> 	I'm sorry, but as there is no longer any "devel" serie, to me
> there is no longer any "stable" serie. Do you mean that we are going
> to get frozen with the same APIs until then end of time ? I don't
> think so...

I mean that proprt procedure for removing APIs needs to be followed,
and that is deprecating them in Doc*/feature-removal-schedule, along
with date, waiting a year, then removing them.

> 	You can see the glass half-full or half-empty. Maybe you can

No, not in this case.
-- 
Thanks for all the (sleeping) penguins.
-
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/