Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755236AbZG2M6q (ORCPT ); Wed, 29 Jul 2009 08:58:46 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1755219AbZG2M6o (ORCPT ); Wed, 29 Jul 2009 08:58:44 -0400 Received: from mail.mnementh.co.uk ([173.45.232.4]:57296 "EHLO mnementh.co.uk" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754781AbZG2M6l (ORCPT ); Wed, 29 Jul 2009 08:58:41 -0400 Message-ID: <4A704777.70001@mnementh.co.uk> Date: Wed, 29 Jul 2009 13:58:31 +0100 From: Ian Molton User-Agent: Mozilla-Thunderbird 2.0.0.19 (X11/20090103) MIME-Version: 1.0 To: Magnus Damm CC: Mark Brown , Guennadi Liakhovetski , linux-kernel@vger.kernel.org, Pierre Ossman , Magnus Damm Subject: Re: MMC: Make the configuration memory resource optional References: <4A6F033B.7030302@mnementh.co.uk> <20090729115817.GA12223@rakim.wolfsonmicro.main> <20090729124233.GA12802@rakim.wolfsonmicro.main> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 657 Lines: 15 Magnus Damm wrote: >> Indeed. It's actually much worse than you say, each individual ARM >> architecture has its own clock API implementation of varying quality and >> of course there are architectures that don't do the clock API at all. > > Yeah. This is exactly why I don't want to block on the clocklib implementation. Yeah, good idea... lets ignore the problem until its so big we cant fix it at all... -- 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/