From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752773AbcGAKAV (ORCPT ); Fri, 1 Jul 2016 06:00:21 -0400 Received: from mezzanine.sirena.org.uk ([106.187.55.193]:33304 "EHLO mezzanine.sirena.org.uk" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752694AbcGAKAS (ORCPT ); Fri, 1 Jul 2016 06:00:18 -0400 Date: Fri, 1 Jul 2016 11:59:43 +0200 From: Mark Brown To: Lee Jones Cc: linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org, kernel@stlinux.com, maxime.coquelin@st.com, patrice.chotard@st.com, mturquette@baylibre.com, sboyd@codeaurora.org, linux-clk@vger.kernel.org, linux-spi@vger.kernel.org Message-ID: <20160701095943.GL6247@sirena.org.uk> References: <20160607111930.10375-1-lee.jones@linaro.org> <20160607111930.10375-7-lee.jones@linaro.org> <20160607151712.GA7510@sirena.org.uk> <20160630205215.GF1707@dell> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="J/pvEKOcHgREgBce" Content-Disposition: inline In-Reply-To: <20160630205215.GF1707@dell> X-Cookie: You are always busy. User-Agent: Mutt/1.6.0 (2016-04-01) X-SA-Exim-Connect-IP: 137.158.23.187 X-SA-Exim-Mail-From: broonie@sirena.org.uk Subject: Re: [PATCH 6/6] spi: st-ssc4: Remove 'no clocking' hack 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 --J/pvEKOcHgREgBce Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Thu, Jun 30, 2016 at 09:52:15PM +0100, Lee Jones wrote: > On Tue, 07 Jun 2016, Mark Brown wrote: > > On Tue, Jun 07, 2016 at 12:19:30PM +0100, Lee Jones wrote: > > > Due to the newly upstreamed 'critical clocks' API we can now > > > safely handle clocking in the SPI and I2C drivers without fear > > > of catastrophically crippling the running platform. > > Acked-by: Mark Brown > We really need to guarantee that this goes in *after* the other > patches have landed, and it looks like they're heading in via their > own respective trees. Any chance you can hold this back and submit it > via your v4.8-fixes submission? I've not applied this patch and had no intention of applying it, the whole point in me acking it was that I was expecting it to get applied as part of the series since AFAICT everything needed to go in together. Your pattern of acking patches you're expecting to be apply yourself is fairly unusual, if it's someone else it's generally safe to assume they're expecting the patch to go via another tree. If this still needs sorting after the merge window please resend it, or ideally it can go in along with the rest of the series via whatever path that's taking. --J/pvEKOcHgREgBce Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQEcBAEBCAAGBQJXdj8NAAoJECTWi3JdVIfQWaYH/0HAssuQfDN6WVtDw6B3EkE1 o6Y3atrxYQQDhPt1t2R1hnB40wwAhyYW8SoicYZhKU91cyn1H5QTmNhGD49ItySM qEeLxXZ9El+f/260hxk60o3lQWMei/Tu8631+kNTQjNPKtxgWFv90uQtaMktWDNF HNiZJukpyxQfFosymm8nHvimEDo8ani8VH5FILaiWawCJlrCNVOuPoVFIcGlpCW1 wclps7EGyqbGDfUqUhm5dyCjx6tCDo2SnCfU9m5BlzmJksUMSrUFXIP8+/Uo34Jw CNp5Vn8yEkNyN1VOgV9lDW307kWqQOMbfSBRQfvN9ONxmxRmLVW5HIPRfepfM6Y= =oFh6 -----END PGP SIGNATURE----- --J/pvEKOcHgREgBce-- From mboxrd@z Thu Jan 1 00:00:00 1970 From: broonie@kernel.org (Mark Brown) Date: Fri, 1 Jul 2016 11:59:43 +0200 Subject: [PATCH 6/6] spi: st-ssc4: Remove 'no clocking' hack In-Reply-To: <20160630205215.GF1707@dell> References: <20160607111930.10375-1-lee.jones@linaro.org> <20160607111930.10375-7-lee.jones@linaro.org> <20160607151712.GA7510@sirena.org.uk> <20160630205215.GF1707@dell> Message-ID: <20160701095943.GL6247@sirena.org.uk> To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org On Thu, Jun 30, 2016 at 09:52:15PM +0100, Lee Jones wrote: > On Tue, 07 Jun 2016, Mark Brown wrote: > > On Tue, Jun 07, 2016 at 12:19:30PM +0100, Lee Jones wrote: > > > Due to the newly upstreamed 'critical clocks' API we can now > > > safely handle clocking in the SPI and I2C drivers without fear > > > of catastrophically crippling the running platform. > > Acked-by: Mark Brown > We really need to guarantee that this goes in *after* the other > patches have landed, and it looks like they're heading in via their > own respective trees. Any chance you can hold this back and submit it > via your v4.8-fixes submission? I've not applied this patch and had no intention of applying it, the whole point in me acking it was that I was expecting it to get applied as part of the series since AFAICT everything needed to go in together. Your pattern of acking patches you're expecting to be apply yourself is fairly unusual, if it's someone else it's generally safe to assume they're expecting the patch to go via another tree. If this still needs sorting after the merge window please resend it, or ideally it can go in along with the rest of the series via whatever path that's taking. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 473 bytes Desc: not available URL: