From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S935023AbcIFXiZ (ORCPT ); Tue, 6 Sep 2016 19:38:25 -0400 Received: from mezzanine.sirena.org.uk ([106.187.55.193]:55236 "EHLO mezzanine.sirena.org.uk" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S933190AbcIFXiV (ORCPT ); Tue, 6 Sep 2016 19:38:21 -0400 Date: Wed, 7 Sep 2016 00:38:06 +0100 From: Mark Brown To: Matthias Kaehlcke Cc: lgirdwood@gmail.com, Douglas Anderson , briannorris@chromium.org, javier@dowhile0.org, robh+dt@kernel.org, mark.rutland@arm.com, linux-kernel@vger.kernel.org, devicetree@vger.kernel.org Message-ID: <20160906233806.GZ3950@sirena.org.uk> References: <20160906210125.GE79728@google.com> <20160906224054.GX3950@sirena.org.uk> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="R4k76f8oNWH5pGim" Content-Disposition: inline In-Reply-To: <20160906224054.GX3950@sirena.org.uk> X-Cookie: FEELINGS are cascading over me!!! User-Agent: Mutt/1.6.0 (2016-04-01) X-SA-Exim-Connect-IP: 81.153.65.142 X-SA-Exim-Mail-From: broonie@sirena.org.uk Subject: Re: [PATCH v4 1/4] regulator: Add set_voltage_time op X-SA-Exim-Version: 4.2.1 (built Mon, 26 Dec 2011 16:24:06 +0000) X-SA-Exim-Scanned: No (on mezzanine.sirena.org.uk); Unknown failure Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org --R4k76f8oNWH5pGim Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Tue, Sep 06, 2016 at 11:40:54PM +0100, Mark Brown wrote: > On Tue, Sep 06, 2016 at 02:01:25PM -0700, Matthias Kaehlcke wrote: > > The new op is analogous to set_voltage_time_sel. It can be used by > > regulators that don't have a table of discrete voltages. The function > I've only got patch 1 in this series, what's going on here? Actually it turns out I have at least three copies of this, one copy of what's hopefully the reset of the series and none of them are threaded together :( You probably want to take a look at your patch sending setup... --R4k76f8oNWH5pGim Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQEcBAEBCAAGBQJXz1NbAAoJECTWi3JdVIfQAcUH/RPzoNwWudVi697VB49zW1sw yC7MvW7MsfoEb2UIEqWJAKcZvimlYdcwi1BeZzDsJ/Ej1Dbo/HVgnZzM7CZ0LAgZ K7Obb8AJWXyDEYUjVDa8WozjzUS3u6CUAfuttP4qP1uFsCGPzQ9FpOBzUnUROHtW tA6TYwP1/XQYQbaE84q8MIESnMbZ8pcS+JyDSboyUjV/jnpPSVwqhsJaqTlMHLtq Vi4uDfnMy8r1nbxD2kePNw58tqVVJQxNhooLzjmYYji7cD6MZNwzQbxJlDz87mtL xtxkz+6otsblQmTW7j7TErNyAGuw/gmOC+x9XairWiat8ThMgohcjMdlKB7zQhU= =TvXT -----END PGP SIGNATURE----- --R4k76f8oNWH5pGim--