From mboxrd@z Thu Jan 1 00:00:00 1970 From: Chris Ball Subject: Re: dw_mmc: Does anyone use multiple slots? Date: Fri, 09 Aug 2013 01:55:44 +0100 Message-ID: <86mworfzsf.fsf@void.printf.net> References: Mime-Version: 1.0 Content-Type: text/plain Return-path: In-Reply-To: (Olof Johansson's message of "Thu, 8 Aug 2013 17:19:44 -0700") Sender: linux-kernel-owner@vger.kernel.org To: Olof Johansson Cc: Doug Anderson , James Hogan , "linux-mmc@vger.kernel.org" , Tomasz Figa , Jaehoon Chung , Seungwon Jeon , Grant Grundler , Alim Akhtar , Abhilash Kesavan , Doug Anderson , linux-samsung-soc , Kukjin Kim , "linux-kernel@vger.kernel.org" , "linux-arm-kernel@lists.infradead.org" , Sonny Rao List-Id: linux-mmc@vger.kernel.org Hi, On Fri, Aug 09 2013, Olof Johansson wrote: > On Thu, Aug 8, 2013 at 5:16 PM, Doug Anderson wrote: > >> I guess my overall question is: if there are no actual implementations >> of multislot, shouldn't we kill it and simplify the code a whole lot? >> If someone out there has a real multislot device they can step back in >> and do it more correctly? >> >> Of course we need to find someone to actually go through and do the >> killing of multislot, but finding that person might be easier if there >> was some agreement that it was good to do. > > There clearly seems to be no in-tree users of multislot. If someone > new comes in, we have the code in the history and can revert the > removal (or at least use it as reference for re-introduction). > > I vote for removing it. It adds really annoying complexity for > something that nobody uses. I agree with Olof, for what it's worth. (The maintainers of the driver are Jaehoon and Seungwon, though.) Thanks, - Chris. -- Chris Ball