Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1757842Ab2HIKrv (ORCPT ); Thu, 9 Aug 2012 06:47:51 -0400 Received: from opensource.wolfsonmicro.com ([80.75.67.52]:52759 "EHLO opensource.wolfsonmicro.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755837Ab2HIKrt (ORCPT ); Thu, 9 Aug 2012 06:47:49 -0400 Date: Thu, 9 Aug 2012 11:47:47 +0100 From: Mark Brown To: Axel Lin Cc: Cyril Chemparathy , "Milo(Woogyom) Kim" , David Dajun Chen , Ashish Jangam , Liam Girdwood , linux-kernel@vger.kernel.org Subject: Re: [PATCH 1/7] regulator: Update comment for set_current_limit callback of struct regulator_ops Message-ID: <20120809104747.GK24328@opensource.wolfsonmicro.com> References: <1344428238.3199.1.camel@phoenix> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1344428238.3199.1.camel@phoenix> X-Cookie: Be different: conform. User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 688 Lines: 13 On Wed, Aug 08, 2012 at 08:17:18PM +0800, Axel Lin wrote: > The regulators should be tending to the maximum in the available range and > consumers should specify the widest range possible. Applied all except 2 and 3. Those are for actual current regulators which are a bit odd here - I'm not really sure they should be in the regulator API at all but their function is very different to the current limits that are normally being specified. -- 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/