Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754074AbdGJNRV (ORCPT ); Mon, 10 Jul 2017 09:17:21 -0400 Received: from bhuna.collabora.co.uk ([46.235.227.227]:41698 "EHLO bhuna.collabora.co.uk" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753563AbdGJNRU (ORCPT ); Mon, 10 Jul 2017 09:17:20 -0400 Date: Mon, 10 Jul 2017 15:17:17 +0200 From: Sebastian Reichel To: Mark Brown Cc: "Alex A. Mihaylov" , Evgeniy Polyakov , Greg Kroah-Hartman , linux-kernel@vger.kernel.org Subject: Re: [PATCH] regmap: regmap-w1: Fix build troubles Message-ID: <20170710131717.grpaai4wjync6g6w@earth> References: <20170707153822.2552-1-minimumlaw@rambler.ru> <20170708145808.6lvtcy3wt3j5zjk2@earth> <20170710103141.teuhsi7o3b4grxjw@sirena.org.uk> <20170710115138.c7dwbhuk7lxbrigg@earth> <20170710121935.aunp4cjnktv57zy4@sirena.org.uk> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="44hms2clbvf2lbca" Content-Disposition: inline In-Reply-To: <20170710121935.aunp4cjnktv57zy4@sirena.org.uk> User-Agent: NeoMutt/20170609 (1.8.3) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2430 Lines: 58 --44hms2clbvf2lbca Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hi, On Mon, Jul 10, 2017 at 01:19:35PM +0100, Mark Brown wrote: > On Mon, Jul 10, 2017 at 01:51:38PM +0200, Sebastian Reichel wrote: > > > Patches like this *really* shouldn't be appearing during the merge > > > window, they should be being handled well before that with everything > > > ready in -next when the merge window opens. >=20 > > Both patches were in linux-next and both patches have been pulled > > by Linus. This is broken *now*. >=20 > Why are none of the build bots finding problems if this is currently > broken and why did this not get fixed in -next when it was introduced? I guess it is because at the moment nothing select REGMAP_W1 in mainline. I did not (yet) queue the power-supply driver, which was the initial reason for adding regmap w1 support. > Like I say I provided a tag for this and didn't get any request to > pull/apply the update in the other direction so it is extremely > disappointing to see that the header move went ahead after that without > the regmap support being included and someone else is having to come > along and clean up the mess. FWIW I am just the messenger, who actually pointed out the issue _before_ it happened in the threads of both patchsets. I expected this to be properly solved by you and Greg. Since this did not work out regmap seems now the logical subsystem for the fix. -- Sebastian --44hms2clbvf2lbca Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAABCgAdFiEE72YNB0Y/i3JqeVQT2O7X88g7+poFAlljfloACgkQ2O7X88g7 +prxvRAAjSCK9n2Wz3RcQigXpHnsD5EpmbvnqHJr+xB4DigWLWpPYupF1ObaZJ90 DreUkchinYxVraagd2rVZ+P9l2b+mea7OYj5Y8g3iTALf1ZCrwHVkci+mTcJ8IE9 N4fAlsHMUAfHeWc2TVroqW++DFdCyi60h8MfLkNWyn3Fc4q00fXLtVcHQhhDHukd mvmQICbG4NxzceiugU84D/ILAO2k9rmBulguqq1g/khZ8ZN6vPFJhrYs0edcB6ow +frMkG/ZyWYAWCdeJl01ULgLGz4R2HsRhHPt/mvCsZlkNHusrLSiaRHJB4m7WMvT ZgR5+VtsSAKtB/P3vriqWQcn+4XnuqyUh11LERiKszfY2KMyTs83DTmZ/sgXJOiY CRWgNOzjq+EqcdG8EOJasmUcgIILzV7s84xn/dzQ6RzcIrQwSekhxGt7G/+3aFqx zic7Umqjdp8FhwdwpCdYBGarNztd3ykJIFw/0aCpgunc30hHBM8xLzmlurtDB6RX d8YIqjmUq1pVjt0THYxel7gzsaV7ebKSoUdsgDyk8GcbHuvn58v0fOs33iRtjgGc kTQHUV+vM4A5gaXpMIjlZkSqz6OzREzU6qkjx7pbaMNE+Rrr3gT4nHdnisaeA0YJ nMIz5qAYu1M+rCeE3ELSPbkjhN8g4xJTmc/J3+uAvLxaym7FtR8= =5/nz -----END PGP SIGNATURE----- --44hms2clbvf2lbca--