From mboxrd@z Thu Jan 1 00:00:00 1970 From: David Laight Date: Thu, 14 May 2020 11:11:34 +0000 Subject: [Ocfs2-devel] remove kernel_setsockopt and kernel_getsockopt In-Reply-To: <20200514103450.GA12901@lst.de> References: <20200513062649.2100053-1-hch@lst.de> <756758e8f0e34e2e97db470609f5fbba@AcuMS.aculab.com> <20200514101838.GA12548@lst.de> <20200514103450.GA12901@lst.de> Message-ID: List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: 'Christoph Hellwig' Cc: 'Joe Perches' , "David S. Miller" , Jakub Kicinski , Eric Dumazet , Alexey Kuznetsov , Hideaki YOSHIFUJI , Vlad Yasevich , Neil Horman , Marcelo Ricardo Leitner , Jon Maloy , Ying Xue , "drbd-dev@lists.linbit.com" , "linux-block@vger.kernel.org" , "linux-kernel@vger.kernel.org" , "linux-rdma@vger.kernel.org" , "linux-nvme@lists.infradead.org" , "target-devel@vger.kernel.org" From: 'Christoph Hellwig' > Sent: 14 May 2020 11:35 > On Thu, May 14, 2020 at 10:26:41AM +0000, David Laight wrote: > > From: Christoph Hellwig > > > Only for those were we have users, and all those are covered. > > > > What do we tell all our users when our kernel SCTP code > > no longer works? > > We only care about in-tree modules, just like for every other interface > in the kernel. Even if our management agreed to release the code and the code layout matched the kernel guidelines you still wouldn't want two large drivers that implement telephony functionality for hardware that very few people actually have. David - Registered Address Lakeside, Bramley Road, Mount Farm, Milton Keynes, MK1 1PT, UK Registration No: 1397386 (Wales)