From: Neil Horman > > In how many years do you plan a removal ... I think we're stuck with uapi > > basically forever as we don't want to break old binaries, no? ;/ > > > I thought we could remove things on a schedule if we followed the deprecation > process, but that may just be for sysfs. Regardless, it would still be nice to > inform people they are using an older api. The issue here is that it is an application API, not a system programming one. I'd guess that most sysfs stuff is only used by programs that are released as part of a Linux distribution - and thus code that is likely to be release with a matching kernel. These sccp structures are much more likely to be used by 'proper' 3rd party applications, targeted at multiple kernel versions - possibly in binary form. We compile applications on the oldest linux version we think our customers are using - otherwise we'd have to release multiple copies. So I don't think they can be deprecated (with warnings from the kernel) for a long time, perhaps 5 or 10 years! The first stage would be (somehow) to generate warnings when applications are compiled. Only when that has been in place for some time would it make sense to generate kernel warnings. David -- To unsubscribe from this list: send the line "unsubscribe linux-sctp" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
