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 [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
