linux-kernel - Re: Please pull 'revert-libertas' 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]

Message-ID: <4640FC76.4090908@garzik.org>
Date:	Tue, 08 May 2007 18:40:54 -0400
From:	Jeff Garzik <jeff@...zik.org>
To:	Dan Williams <dcbw@...hat.com>
CC:	David Miller <davem@...emloft.net>, penberg@...helsinki.fi,
	linville@...driver.com, hch@...radead.org,
	linux-wireless@...r.kernel.org, marcelo@...ck.org,
	linux-kernel@...r.kernel.org, akpm@...ux-foundation.org,
	torvalds@...ux-foundation.org
Subject: Re: Please pull 'revert-libertas' branch of wireless-2.6

Dan Williams wrote:
> I'll audit the list of ioctls and remove ones that may be objectionable,
> and we'll go back through them after 2.6.22 and add back in ones that
> are actually required.  Keep the API/ABI small and expand if necessary.
> What's the timeframe required here?  Linville said a few days at the
> most.

Ideally, before 2.6.22-rc1.  No set date, but generally it's a week or 
two after merge window opens.

But even if you miss -rc1, we MUST get in the ioctl removal before 
2.6.22 release.  This is certainly exception to the "nothing but bug 
fixes" rule -- or perhaps it is following the rule, if you consider the 
ioctls' existence a bug :)

Getting the CodingStyle fixes in before 2.6.22-rc1 would be nice, but, 
as I noted, lower priority than serious stuff like ioctl consideration.

	Jeff

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