From mboxrd@z Thu Jan 1 00:00:00 1970 From: Mark Brown Subject: Re: [PATCH v10 00/13] arm64: Branch Target Identification support Date: Tue, 28 Apr 2020 16:58:12 +0100 Message-ID: <20200428155808.GJ5677@sirena.org.uk> References: <20200316165055.31179-1-broonie@kernel.org> <20200422154436.GJ4898@sirena.org.uk> <20200422162954.GF3585@gaia> <20200428132804.GF6791@willie-the-truck> <20200428151205.GH5677@sirena.org.uk> <20200428151815.GB12697@willie-the-truck> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="GvznHscUikHnwW2p" Return-path: Received: from mail.kernel.org ([198.145.29.99]:54488 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1728225AbgD1P6P (ORCPT ); Tue, 28 Apr 2020 11:58:15 -0400 Content-Disposition: inline In-Reply-To: <20200428151815.GB12697@willie-the-truck> Sender: linux-arch-owner@vger.kernel.org List-ID: To: Will Deacon Cc: Catalin Marinas , Alexander Viro , Paul Elliott , Peter Zijlstra , Yu-cheng Yu , Amit Kachhap , Vincenzo Frascino , Marc Zyngier , Eugene Syromiatnikov , Szabolcs Nagy , "H . J . Lu " , Andrew Jones , Kees Cook , Arnd Bergmann , Jann Horn , Richard Henderson , Kristina =?utf-8?Q?Mart=C5=A1enko?= , Thomas Gleixner , Florian Weimer S --GvznHscUikHnwW2p Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Tue, Apr 28, 2020 at 04:18:16PM +0100, Will Deacon wrote: > On Tue, Apr 28, 2020 at 04:12:05PM +0100, Mark Brown wrote: > > It's probably easier for me if you just use the existing branch, I've > > already got a branch based on a merge down. > Okey doke, I'll funnel that in the direction of linux-next then. It does > mean that any subsequent patches for 5.8 that depend on BTI will need to > be based on this branch, so as long as you're ok with that then it's fine > by me (since I won't be able to apply patches if they refer to changes > introduced in the recent merge window). That's not a problem, that's what I've got already and if I try to send everything based off -rc3 directly the series would get unmanagably large. Actually unless you think it's a bad idea I think what I'll do is go and send out a couple of the preparatory changes (the insn updates and the last bit of annotation conversions) separately for that branch while I finalize the revisions of the main BTI kernel bit, hopefully that'll make the review a bit more approachable. --GvznHscUikHnwW2p Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQEzBAABCgAdFiEEreZoqmdXGLWf4p/qJNaLcl1Uh9AFAl6oUo8ACgkQJNaLcl1U h9ANJwf/WRlo08Mn6rULa8b3pqa1bQzdRN/zAGUfNf93UHKMH2yvxQZ6GTGie8us Kw24VCNz5n7f6AjcO0v+vH6pAJxlD2DHraSawXDaEKZJ2YMnFSryzWFrWJr12klT DRRRi3+D2+GBFPflADAl2YaCfEV9D2USZGPG6OB/gkF43dmK1VIAon0ixx8WL7dw GtmV9U8DZlC9FrJd7gh9jbJGYiIgZ7hcMR2eyuzH5Z2gW4WPwWOkfd+pc9eBuyNl vbBauk5tAYnPssGMtNUG7M9gakg5U1GsRBY7E1QUJ97iMAUqiKN2Z1mharmqU6cs sswMEKQMo98MespYoImEM/wHQ5GqJw== =KIkv -----END PGP SIGNATURE----- --GvznHscUikHnwW2p-- From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail.kernel.org ([198.145.29.99]:54488 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1728225AbgD1P6P (ORCPT ); Tue, 28 Apr 2020 11:58:15 -0400 Date: Tue, 28 Apr 2020 16:58:12 +0100 From: Mark Brown Subject: Re: [PATCH v10 00/13] arm64: Branch Target Identification support Message-ID: <20200428155808.GJ5677@sirena.org.uk> References: <20200316165055.31179-1-broonie@kernel.org> <20200422154436.GJ4898@sirena.org.uk> <20200422162954.GF3585@gaia> <20200428132804.GF6791@willie-the-truck> <20200428151205.GH5677@sirena.org.uk> <20200428151815.GB12697@willie-the-truck> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="GvznHscUikHnwW2p" Content-Disposition: inline In-Reply-To: <20200428151815.GB12697@willie-the-truck> Sender: linux-arch-owner@vger.kernel.org List-ID: To: Will Deacon Cc: Catalin Marinas , Alexander Viro , Paul Elliott , Peter Zijlstra , Yu-cheng Yu , Amit Kachhap , Vincenzo Frascino , Marc Zyngier , Eugene Syromiatnikov , Szabolcs Nagy , "H . J . Lu " , Andrew Jones , Kees Cook , Arnd Bergmann , Jann Horn , Richard Henderson , Kristina =?utf-8?Q?Mart=C5=A1enko?= , Thomas Gleixner , Florian Weimer , Sudakshina Das , linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org, linux-arch@vger.kernel.org, linux-fsdevel@vger.kernel.org Message-ID: <20200428155812.1-0WU-o50wdM1447cAW5A2WHY4PXUb7TKAD4U16AIIg@z> --GvznHscUikHnwW2p Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Tue, Apr 28, 2020 at 04:18:16PM +0100, Will Deacon wrote: > On Tue, Apr 28, 2020 at 04:12:05PM +0100, Mark Brown wrote: > > It's probably easier for me if you just use the existing branch, I've > > already got a branch based on a merge down. > Okey doke, I'll funnel that in the direction of linux-next then. It does > mean that any subsequent patches for 5.8 that depend on BTI will need to > be based on this branch, so as long as you're ok with that then it's fine > by me (since I won't be able to apply patches if they refer to changes > introduced in the recent merge window). That's not a problem, that's what I've got already and if I try to send everything based off -rc3 directly the series would get unmanagably large. Actually unless you think it's a bad idea I think what I'll do is go and send out a couple of the preparatory changes (the insn updates and the last bit of annotation conversions) separately for that branch while I finalize the revisions of the main BTI kernel bit, hopefully that'll make the review a bit more approachable. --GvznHscUikHnwW2p Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQEzBAABCgAdFiEEreZoqmdXGLWf4p/qJNaLcl1Uh9AFAl6oUo8ACgkQJNaLcl1U h9ANJwf/WRlo08Mn6rULa8b3pqa1bQzdRN/zAGUfNf93UHKMH2yvxQZ6GTGie8us Kw24VCNz5n7f6AjcO0v+vH6pAJxlD2DHraSawXDaEKZJ2YMnFSryzWFrWJr12klT DRRRi3+D2+GBFPflADAl2YaCfEV9D2USZGPG6OB/gkF43dmK1VIAon0ixx8WL7dw GtmV9U8DZlC9FrJd7gh9jbJGYiIgZ7hcMR2eyuzH5Z2gW4WPwWOkfd+pc9eBuyNl vbBauk5tAYnPssGMtNUG7M9gakg5U1GsRBY7E1QUJ97iMAUqiKN2Z1mharmqU6cs sswMEKQMo98MespYoImEM/wHQ5GqJw== =KIkv -----END PGP SIGNATURE----- --GvznHscUikHnwW2p--