Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S966990Ab3HIATq (ORCPT ); Thu, 8 Aug 2013 20:19:46 -0400 Received: from mail-qc0-f179.google.com ([209.85.216.179]:42051 "EHLO mail-qc0-f179.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S966940Ab3HIATp (ORCPT ); Thu, 8 Aug 2013 20:19:45 -0400 MIME-Version: 1.0 X-Originating-IP: [2620:0:1000:1b02:6e3b:e5ff:fe16:f1aa] In-Reply-To: References: Date: Thu, 8 Aug 2013 17:19:44 -0700 Message-ID: Subject: Re: dw_mmc: Does anyone use multiple slots? From: Olof Johansson To: Doug Anderson Cc: James Hogan , "linux-mmc@vger.kernel.org" , Chris Ball , 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 Content-Type: text/plain; charset=ISO-8859-1 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1054 Lines: 25 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. -Olof -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/