From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S934098AbdA0LQi (ORCPT ); Fri, 27 Jan 2017 06:16:38 -0500 Received: from atrey.karlin.mff.cuni.cz ([195.113.26.193]:49864 "EHLO atrey.karlin.mff.cuni.cz" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S933401AbdA0LQd (ORCPT ); Fri, 27 Jan 2017 06:16:33 -0500 Date: Fri, 27 Jan 2017 12:16:26 +0100 From: Pavel Machek To: Guenter Roeck Cc: Zhang Rui , Pali =?iso-8859-1?Q?Roh=E1r?= , sre@kernel.org, kernel list , linux-arm-kernel , linux-omap@vger.kernel.org, tony@atomide.com, khilman@kernel.org, aaro.koskinen@iki.fi, ivo.g.dimitrov.75@gmail.com, patrikbachan@gmail.com, serge@hallyn.com, abcloriens@gmail.com, fabio.estevam@nxp.com Subject: Re: v4.10-rc4 to v4.10-rc5: battery regression on Nokia N900 Message-ID: <20170127111626.GB5335@amd> References: <20170124073720.GB5603@amd> <88c94ea6-abe2-0f20-337e-e9ee00c883d8@roeck-us.net> <20170124175800.GA15070@amd> <20170124184526.GA25056@roeck-us.net> <20170125111233.GB3912@amd> <20170125120918.GA7936@pali> <1485481030.2469.15.camel@intel.com> <1485488382.2469.27.camel@intel.com> <9146145b-7e21-c4de-a9cd-dad7bc74ee7a@roeck-us.net> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="2B/JsCI69OhZNC5r" Content-Disposition: inline In-Reply-To: <9146145b-7e21-c4de-a9cd-dad7bc74ee7a@roeck-us.net> User-Agent: Mutt/1.5.23 (2014-03-12) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org --2B/JsCI69OhZNC5r Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hi! > >>That sounds like fun. Changing bq27200-0 to bq27200_0 is Forbidden by > >>the ABI Police, but taking the entire device away is ok. Changing bq27200-0 to bq27200_0 is forbidden in -rc6 time. If you believe noone depends on the name, argue your case, and it might be possible to change it in -rc0. If someone uses the name, they care about the device, and you can't take it away. > >No. IMO, it depends on if the interface is used or not. > >If hwmon I/F is used, we can not take it away, nor change its name. >=20 > Even if the use doesn't depend on that name ? If the use doesn't depend on the name, you may get away with changing the name. (But not in -rc6.) > >If thermal zone I/F is used, we can not change it's 'type' name to be > >compatible with new hwmon API. >=20 > You mean you can not fix the name to be compatible with libsensors. >=20 > Makes me wonder if there shouldn't be a rule that exploits must not > be fixed if already exploited. That is not useful argumentation. Pavel --=20 (english) http://www.livejournal.com/~pavelmachek (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blo= g.html --2B/JsCI69OhZNC5r Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Digital signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iEYEARECAAYFAliLLAoACgkQMOfwapXb+vKSXwCglSkXi4dpxH2esWUTYWrMpOZ4 R5AAn3jnC2XEf/B4vC3rm/3oiXv27HK3 =yLyd -----END PGP SIGNATURE----- --2B/JsCI69OhZNC5r--