From mboxrd@z Thu Jan 1 00:00:00 1970 From: Olof Johansson Subject: Re: [PATCH v4 5/5] mmc: dw_mmc: Remove DW_MCI_QUIRK_NO_WRITE_PROTECT Date: Mon, 14 Jan 2013 22:28:13 -0800 Message-ID: <20130115062813.GD20105@quad.lixom.net> References: <1357842269-15062-1-git-send-email-dianders@chromium.org> <1357923834-31641-1-git-send-email-dianders@chromium.org> <1357923834-31641-5-git-send-email-dianders@chromium.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: <1357923834-31641-5-git-send-email-dianders@chromium.org> Sender: linux-samsung-soc-owner@vger.kernel.org To: Doug Anderson Cc: linux-mmc@vger.kernel.org, linux-samsung-soc@vger.kernel.org, Thomas Abraham , Kukjin Kim , Arnd Bergmann , Will Newton , Chris Ball , Jaehoon Chung , Seungwon Jeon , linux-kernel@vger.kernel.org, Kyungmin Park List-Id: linux-mmc@vger.kernel.org On Fri, Jan 11, 2013 at 09:03:54AM -0800, Doug Anderson wrote: > The original quirk was added in the change 'mmc: dw_mmc: add quirk to > indicate missing write protect line'. The original quirk was added at > a controller level even though each slot has its own write protect (so > the quirk should be at the slot level). A recent change (mmc: dw_mmc: > Add "disable-wp" device tree property) added a slot-level quirk and > support for the quirk directly to dw_mmc. > > Signed-off-by: Doug Anderson Acked-by: Olof Johansson