Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753937AbdGJMTx (ORCPT ); Mon, 10 Jul 2017 08:19:53 -0400 Received: from mezzanine.sirena.org.uk ([106.187.55.193]:37058 "EHLO mezzanine.sirena.org.uk" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753657AbdGJMTw (ORCPT ); Mon, 10 Jul 2017 08:19:52 -0400 Date: Mon, 10 Jul 2017 13:19:35 +0100 From: Mark Brown To: Sebastian Reichel Cc: "Alex A. Mihaylov" , Evgeniy Polyakov , Greg Kroah-Hartman , linux-kernel@vger.kernel.org Message-ID: <20170710121935.aunp4cjnktv57zy4@sirena.org.uk> References: <20170707153822.2552-1-minimumlaw@rambler.ru> <20170708145808.6lvtcy3wt3j5zjk2@earth> <20170710103141.teuhsi7o3b4grxjw@sirena.org.uk> <20170710115138.c7dwbhuk7lxbrigg@earth> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="isixd26td7sqycst" Content-Disposition: inline In-Reply-To: <20170710115138.c7dwbhuk7lxbrigg@earth> User-Agent: NeoMutt/20170609 (1.8.3) X-SA-Exim-Connect-IP: 2001:470:1f1d:6b5::3 X-SA-Exim-Mail-From: broonie@sirena.org.uk Subject: Re: [PATCH] regmap: regmap-w1: Fix build troubles X-SA-Exim-Version: 4.2.1 (built Tue, 02 Aug 2016 21:08:31 +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 Content-Length: 1492 Lines: 39 --isixd26td7sqycst Content-Type: text/plain; charset=us-ascii Content-Disposition: inline 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. > Both patches were in linux-next and both patches have been pulled > by Linus. This is broken *now*. 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? 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. --isixd26td7sqycst Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQEzBAABCAAdFiEEreZoqmdXGLWf4p/qJNaLcl1Uh9AFAlljcNYACgkQJNaLcl1U h9CgOwgAhaJzLv+OOKRMkZtyaE2GY7ZGFREHws1F65pEyQG/TP085Y0pLCYV4vfr 34HyPU0g9Wc1wtCzgJBfsOD0B9rwX6UMOEe2bz39Cg6v+OwtvfyWcw6zKj9Gim8A ATWaE836UsGLeRa3Po4To29Pv+DUssUnkmwK++sEfW196tUdaX3wypyz/wUMV3dR MFq/FzPqg/xgmesEOYIKka9PXiUbWTI57IHbOuys1iBdJwN7NiN1VkbVdJ7erTGS eXd1wNbzRqyZagRIBqtS6S5mcBHoKNKpdu1UR5Or2wkBjuK0+ozQ/2zAcy2zc+Yi 4ATbkATwHLraf4s15nKPryahTpL50A== =qdmO -----END PGP SIGNATURE----- --isixd26td7sqycst--