From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Steve Wise" Subject: RE: Upcoming libibverbs release Date: Wed, 29 Jun 2016 15:44:31 -0500 Message-ID: <018f01d1d247$09857ff0$1c907fd0$@opengridcomputing.com> References: <3b89c411-72be-ddc5-5ebf-009eeee29692@redhat.com> <4ec1d8e6-a908-bb49-a137-415856ec6faa@dev.mellanox.co.il> <20160627181758.GD23540@obsidianresearch.com> <20160628050246.GB3584@leon.nu> <20160628162028.GA27518@obsidianresearch.com> <20160628170549.GE3584@leon.nu> <20160628211858.GB5786@obsidianresearch.com> <20160629120920.GA24151@infradead.org> <20160629183414.GD17031@obsidianresearch.com> <017301d1d236$8496b030$8dc41090$@opengridcomputing.com> <20160629185757.GA17839@obsidianresearch.com> <017801d1d23a$a3836b10$ea8a4130$@opengridcomputing.com> <1828884A29C6694DAF28B7E6B8A82373AB06699A@ORSMSX109.amr.corp.intel.com> <017f01d1d23b$f27c4970$d774dc50$@opengridcomputing.com> <1828884A29C6694DAF28B7E6B8A82373AB0669F5@ORSMSX109.amr.corp.intel.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <1828884A29C6694DAF28B7E6B8A82373AB0669F5-P5GAC/sN6hkd3b2yrw5b5LfspsVTdybXVpNB7YpNyf8@public.gmane.org> Content-Language: en-us Sender: linux-rdma-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org To: "'Hefty, Sean'" , 'Jason Gunthorpe' Cc: 'Christoph Hellwig' , 'Leon Romanovsky' , 'Yishai Hadas' , 'Doug Ledford' , 'linux-rdma' , 'Yishai Hadas' , 'Matan Barak' , 'Majd Dibbiny' , talal-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org List-Id: linux-rdma@vger.kernel.org > > > But, even if you didn't have this, this would just follow the same > > release > > procedure > > > that is used by the kernel. > > > > What do you mean? > > You don't have individual releases for the kernel drivers. They all just get grouped > into the next kernel release. > Yes, and packaging all this into one libuberverbs is fine, as long as we can do point/bug fix releases as needed when individual providers have key fixes they need pushed into distros... > FWIW, libfabric uses a single repo, and actually builds the providers directly into the > library. That model has been working fine, and the benefits far away the negatives. > I think the concern here is being overstated -- 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