From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S934680AbbDIJgI (ORCPT ); Thu, 9 Apr 2015 05:36:08 -0400 Received: from mezzanine.sirena.org.uk ([106.187.55.193]:58547 "EHLO mezzanine.sirena.org.uk" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932881AbbDIJgE (ORCPT ); Thu, 9 Apr 2015 05:36:04 -0400 Date: Thu, 9 Apr 2015 10:35:56 +0100 From: Mark Brown To: Stephen Rothwell Cc: Liam Girdwood , linux-next@vger.kernel.org, linux-kernel@vger.kernel.org, Hai Li , Rob Clark , Dave Airlie , Bjorn Andersson Message-ID: <20150409093556.GP6023@sirena.org.uk> References: <20150409143309.3a1fac67@canb.auug.org.au> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="PJ8DlcwO9+aeSqwG" Content-Disposition: inline In-Reply-To: <20150409143309.3a1fac67@canb.auug.org.au> X-Cookie: I've been there. User-Agent: Mutt/1.5.23 (2014-03-12) X-SA-Exim-Connect-IP: 94.175.94.161 X-SA-Exim-Mail-From: broonie@sirena.org.uk Subject: Re: linux-next: build failure after merge of the regulator tree 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 --PJ8DlcwO9+aeSqwG Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Thu, Apr 09, 2015 at 02:33:09PM +1000, Stephen Rothwell wrote: > After merging the regulator tree, today's linux-next build (arm multi_v7_defconfig) > failed like this: > drivers/gpu/drm/msm/dsi/dsi_host.c: In function 'dsi_host_regulator_disable': > drivers/gpu/drm/msm/dsi/dsi_host.c:330:4: error: implicit declaration of function 'regulator_set_optimum_mode' [-Werror=implicit-function-declaration] > regulator_set_optimum_mode(s[i].consumer, > ^ > Caused by commit a689554ba6ed ("drm/msm: Initial add DSI connector > support") from the drm tree interacting with commit ae6e808f1574 > ("regulator: Drop temporary regulator_set_optimum_mode wrapper") from > the regulator tree. > This happens every time someone renames/changes an API :-( It's *really* questionable if anyone should be using that API in the first place, one of the reasons it's being removed is that it's really unclear that anything would be able to successfully use it as-is. The easist thing might be to drop the new usage for the time being. --PJ8DlcwO9+aeSqwG Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Digital signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQEcBAEBCAAGBQJVJkf8AAoJECTWi3JdVIfQ+2EH/iRSq2bqm52kSURY7TP+X93q n38q1bvtdNMXSzKfEmyUZ9PuUEnWvRwBkJ3f/ZjgfegBTnlMz0ZYF00mVuuu2ddw tiRytvVtsfdTbCFL7qWsjWHWD8k4UOP5PGXpjA29Af6E8dkmkMSqqmHTddxCdA/B VQng9LskN/ZFio94iqik9eKnLalPoBDywmW1xW8NjWaom812yXpzDdudODqftSxV AEqvnjRy8cWjHuK3S/akwmdTZ66fmWTMI9P3PsSbxhUPGq/dCdzo/7nWcoh20IO5 3YyzBHaJdiHZa2t7a5Rbb8lDxG35OGPIGNs+2BQIdibsLa34w0QcamuKEpQty/M= =hkDV -----END PGP SIGNATURE----- --PJ8DlcwO9+aeSqwG--