From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jason Gunthorpe Subject: Re: rdma-core stable releases Date: Mon, 13 Nov 2017 12:13:11 -0700 Message-ID: <20171113191311.GG6918@ziepe.ca> References: <20171106182756.GD18802@ziepe.ca> <6012d1c3-cd18-25e8-c5ae-3d678142177b@suse.de> <54347E5A035A054EAE9D05927FB467F9B61778A9@ORSMSX101.amr.corp.intel.com> <20171110202455.GP18825@mtr-leonro.local> <20171110211448.GF17451@ziepe.ca> <1eba9063-80a4-ad9d-4adf-93770b9ed7c9@suse.de> <20171113070856.GZ18825@mtr-leonro.local> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: Sender: linux-rdma-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org To: "Amrani, Ram" Cc: Leon Romanovsky , Nicolas Morey-Chaisemartin , "Davis, Arlin R" , "Kalderon, Michal" , "linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org" , Doug Ledford , "Elior, Ariel" , "Rahman, Ameen" , "Radzi, Amit" List-Id: linux-rdma@vger.kernel.org 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%. Anything else is madness and people will start to ask for backpointing features and other crazy things to -stable. Jason -- To unsubscribe from this list: send the line "unsubscribe linux-rdma" in the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org More majordomo info at http://vger.kernel.org/majordomo-info.html