From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1030753AbdIZNVj (ORCPT ); Tue, 26 Sep 2017 09:21:39 -0400 Received: from smtp.nue.novell.com ([195.135.221.5]:60998 "EHLO smtp.nue.novell.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S935006AbdIZNVi (ORCPT ); Tue, 26 Sep 2017 09:21:38 -0400 Date: Tue, 26 Sep 2017 15:21:34 +0200 From: Felix Schnizlein To: Mark Rutland Cc: Will Deacon , gregkh@linuxfoundation.org, trenn@suse.com, catalin.marinas@arm.com, sfr@canb.auug.org.au, linux@armlinux.org.uk, linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org, tglx@linutronix.de Subject: Re: Unreviewed arm64 ABI change in linux-next via driver-core tree Message-ID: <20170926132134.6ekk44ezeehovppe@angmar> References: <20170926124536.GA11192@arm.com> <20170926131525.GE15480@leverpostej> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="chsxtslaun773puk" Content-Disposition: inline In-Reply-To: <20170926131525.GE15480@leverpostej> Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org --chsxtslaun773puk Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On 26.09.17, Mark Rutland wrote: > Hi, >=20 > On Tue, Sep 26, 2017 at 01:45:37PM +0100, Will Deacon wrote: > > Hi Greg, > >=20 > > We stumbled over a change in linux-next that has ABI implications for a= rm64 > > and, as far as we can tell, has not been reviewed: > >=20 > > https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/com= mit/arch/arm64/kernel?id=3Dfb7ff3f8721b87bf078868c9a252fa0cf71a47c2 > >=20 > > ("fb7ff3f8721b cpuinfo: implement sysfs nodes for arm64") >=20 > > Please can you drop this from your tree until we've had a chance to rev= iew > > it properly? If Felix can repost it as above, then we can get the discu= ssion > > started because, aside from this email, we have concerns about exactly = what > > is being exposed to userspace here. >=20 > Seconded. >=20 > Experience with the existing /proc/cpuinfo shows that this needs *very* > careful review. >=20 > I've worked on arm64's /proc/cpuinfo, and I'd appreciate being Cc'd on > future postings of this series. I'd also recommend that future postings > are also Cc'd to linux-arch (and maybe linux-api) so that the interface > is reviewed by a larger set of relevant parties. I will do that! >=20 > Thanks, > Mark. --chsxtslaun773puk Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQEzBAEBCAAdFiEECcIUp05v5BnDsR6tT4AWTCp2DB0FAlnKVFkACgkQT4AWTCp2 DB3GkAf+PGfp0PG7/15zu7l35PxxWGg98+Hw2YJw8aL7UrU53bapvocyt9aVLuir zZ/OE7v0Th1v2ObFP9n84EerNGTrEMcDJXJapRlv8/oUAdb2FFqrWqC7VcDk5MVv 4/iHvayR12xy/Ng0idbrJUnB8GVN4k0ZG1UpoVsIhCcVlyKMK3IryopEVVlXWSUh l+WKtcFLH573ePaqWunfXvZbKbidAsmA3wpmIQzuMc5X/Iq11J4Yzsg9D4/GFlPE w3RTUXYiN1UiC7DJzTvwmaTuLSIxvEhnCX6L6LtdB8e87FdLrJdSiw+ChC+gVh7J /afYRX9+pZzgGmwGV0WDto4uvkY3XA== =fAQ8 -----END PGP SIGNATURE----- --chsxtslaun773puk--