On Mon, 10 Sep 2007 02:23:24 -0700 Andrew Morton <akpm@linux-foundation.org> wrote:here's the skinny: 99% of the external module developers won't notice until they're gone, even with the warning. And that's an optimistic estimate. Warnings don't work for this. All this kind of thing buys us is an excuse so that we can say "but we warned you for 3 months". It doesn't actually change anything else. Maybe I'm too pessimistic in my assumption that external open module writers don't actually follow mainline closely; and maybe part of me would love for them to follow it closer, so close that they would even consider submitting their driver for it. But sadly from experience... warnings dont' work. Only when things break hard people notice. -
| Tarkan Erimer | Re: Dual-Licensing Linux Kernel with GPL V2 and GPL V3 |
| Greg KH | [GIT PATCH] driver core patches against 2.6.24 |
| James Bottomley | Re: Announce: Linux-next (Or Andrew's dream :-)) |
| Trent Piepho | Re: [PATCH] fakephp: Allocate PCI resources before adding the device |
| Antonio Almeida | HTB accuracy for high speed |
| David Miller | [GIT]: Networking |
| Gerrit Renker | [PATCH 27/37] dccp: Integration of dynamic feature activation - part 2 (server side) |
| Jarek Poplawski | [PATCH] pkt_sched: Destroy gen estimators under rtnl_lock(). |
git: | |
