linux-kernel - Re: [RFCLUE3] flagging kernel interface changes

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: <455BB95E.8090600@serpentine.com>
Date:	Wed, 15 Nov 2006 17:05:34 -0800
From:	Bryan O'Sullivan <bos@...pentine.com>
To:	William D Waddington <william.waddington@...zmo.com>
CC:	Arjan van de Ven <arjan@...radead.org>,
	linux-kernel@...r.kernel.org
Subject: Re: [RFCLUE3] flagging kernel interface changes

William D Waddington wrote:

> The other part of the question is why this irq_handler prototype change
> in 2.6.19 isn't flagged to make things a little easier.

For in-tree drivers, it broke the compilation of any drivers that relied 
upon it, and they were then fixed, and most of the fixing occurred 
before the changes made it into any widely used tree.  That 
break-it-and-fix-it approach is typically seen as flagging enough.  If 
your driver isn't in-tree, it's invisible to kernel maintainers.

For out-of-tree drivers, your best bet is to follow Jonathan Corbet's 
notes on LWN.  He's pretty good about describing impending widespread 
breakage before it hits the main tree.

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