On Mon, Nov 13, 2017 at 12:13:11PM -0700, Jason Gunthorpe wrote: > On Mon, Nov 13, 2017 at 08:47:10AM +0000, Amrani, Ram wrote: > > > It is logical that ABI version changes won't be supported. As well as new features that affect the ABI. > > Still, I would like to have the following fix ability - > > Use a bit in an existing u32, via adding an entry to an existing enum. > > I can imagine this being used as a feature disable/enable. > > No. > > No ABI change means no new symbols in the public header files, no > changes in manual pages and no 'backwards compatible' changes. No > ABI changes at all. > > Only mainline can have ABI changes, and the -stable should be > completely compatible up and down all stable releases. Compiling > against 15.9 should continue to load and work with the same feature > set 100%. +1 This is the whole idea of -stable branch. > > Anything else is madness and people will start to ask for backpointing > features and other crazy things to -stable. > > Jason
Attachment:
signature.asc
Description: PGP signature
