From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755989AbbJAL3q (ORCPT ); Thu, 1 Oct 2015 07:29:46 -0400 Received: from mezzanine.sirena.org.uk ([106.187.55.193]:34163 "EHLO mezzanine.sirena.org.uk" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755655AbbJAL3e (ORCPT ); Thu, 1 Oct 2015 07:29:34 -0400 Date: Thu, 1 Oct 2015 12:29:26 +0100 From: Mark Brown To: Sascha Hauer Cc: linux-kernel@vger.kernel.org, Liam Girdwood , kernel@pengutronix.de, linux-arm-kernel@lists.infradead.org Message-ID: <20151001112926.GG12635@sirena.org.uk> References: <1443621946-8712-1-git-send-email-s.hauer@pengutronix.de> <1443621946-8712-4-git-send-email-s.hauer@pengutronix.de> <20150930223603.GF15635@sirena.org.uk> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="vJguvTgX93MxBIIe" Content-Disposition: inline In-Reply-To: <20150930223603.GF15635@sirena.org.uk> X-Cookie: Walk softly and carry a megawatt laser. User-Agent: Mutt/1.5.23 (2014-03-12) X-SA-Exim-Connect-IP: 2a01:348:6:8808:7e7a:91ff:fede:4a45 X-SA-Exim-Mail-From: broonie@sirena.org.uk Subject: Re: [PATCH 3/6] regulator: core: create unlocked version of regulator_list_voltage X-SA-Exim-Version: 4.2.1 (built Mon, 26 Dec 2011 16:24:06 +0000) X-SA-Exim-Scanned: Yes (on mezzanine.sirena.org.uk) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org --vJguvTgX93MxBIIe Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Sep 30, 2015 at 11:36:03PM +0100, Mark Brown wrote: > On Wed, Sep 30, 2015 at 04:05:43PM +0200, Sascha Hauer wrote: > > The unlocked version will be needed when we start propagating voltage > > changes to the supply regulators. >=20 > I'm now wondering why we have a locked _list_voltage() in the first > place... it *should* be a pure function that doesn't need any locking. > I'll check tomorrow if there are any users who care but if there aren't > the change here is probably to remove the locking entirely. Hrm, looks like there's one that *might* need it - let's go with this for now, we can always fix up later. --vJguvTgX93MxBIIe Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Digital signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQEcBAEBCAAGBQJWDRkVAAoJECTWi3JdVIfQlhQH/17u1pfzbsndTvhSHs8ku6M7 kJoueCtUcDaZzSkGNU0TQdzTTe2QmNahWRKJ8M/uslrNbCZZYs5JZAum82Fha74f u+//9E4SnxP7muwyI7iRZVGGy01JQpOr+SKy6sqMfrZFIwYFK0Jp9X5Ez1rqaS6q ouC6iWJl/im2igHQ5ETKEK5NSig9L0ZHOhlKD+Rb0P46D990wyQgmALxdZx2ln+X R9VXOX0I9YFhFBXFx0QCUUIA8uImrX08iiygazRUwC7w32ncmUTrLEHzK5G7CQSd Q6hvTCrNlijeBCgl94pN6gveXC70BZNCH9T5XDw9utGnOrndCS3gI1Ftl1TUfmQ= =utk8 -----END PGP SIGNATURE----- --vJguvTgX93MxBIIe--