From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
        id S1754499AbdIZM5F (ORCPT <rfc822;w@1wt.eu>);
        Tue, 26 Sep 2017 08:57:05 -0400
Received: from smtp.nue.novell.com ([195.135.221.5]:52814 "EHLO
        smtp.nue.novell.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
        with ESMTP id S1753211AbdIZM5E (ORCPT
        <rfc822;groupwise-linux-kernel@vger.kernel.org:0:0>);
        Tue, 26 Sep 2017 08:57:04 -0400
Date: Tue, 26 Sep 2017 14:57:01 +0200
From: Felix Schnizlein <fschnizlein@suse.com>
To: Will Deacon <will.deacon@arm.com>
Cc: gregkh@linuxfoundation.org, trenn@suse.com, catalin.marinas@arm.com,
        sfr@canb.auug.org.au, mark.rutland@arm.com, 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: <20170926125701.k7hqdt5pbkolkhak@angmar>
References: <20170926124536.GA11192@arm.com>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha256;
        protocol="application/pgp-signature"; boundary="werduicoa52qw56n"
Content-Disposition: inline
In-Reply-To: <20170926124536.GA11192@arm.com>
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org


--werduicoa52qw56n
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

Hi Will, Hi Greg,

It seems this is all my fault. It looks like forgot to check that the
outgoing mailserver send the patches correctly to the mailinglists which
doesn't happen.

So to make this horrible situation short maybe drop the patches and I
will resend them and make sure this time everything works as expected

Sorry Greg for all the stress :(

Felix
On 26.09.17, Will Deacon wrote:
> Hi Greg,
>=20
> We stumbled over a change in linux-next that has ABI implications for arm=
64
> 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/commi=
t/arch/arm64/kernel?id=3Dfb7ff3f8721b87bf078868c9a252fa0cf71a47c2
>=20
> ("fb7ff3f8721b cpuinfo: implement sysfs nodes for arm64")
>=20
> It looks like this was requested by you on LKML here:
>=20
> https://lkml.org/lkml/2017/8/2/663
>=20
> but these sorts of changes really need to go on the linux-arm-kernel mail=
ing
> list with the maintainers on cc so that the patches can be properly revie=
wed
> and eventually acked if appropriate. In this case, I can't find any trace=
 of
> the patch on any of the mailing lists to which I'm subscribed.
>=20
> Please can you drop this from your tree until we've had a chance to review
> it properly? If Felix can repost it as above, then we can get the discuss=
ion
> started because, aside from this email, we have concerns about exactly wh=
at
> is being exposed to userspace here.
>=20
> Thanks,
>=20
> Will
>=20

--werduicoa52qw56n
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQEzBAEBCAAdFiEECcIUp05v5BnDsR6tT4AWTCp2DB0FAlnKTpUACgkQT4AWTCp2
DB1cIAf8CL7FFjkkW+k8ZPiy15mVdtQrs5y/1m2sYdI00nUBwiCgeui5+NvYVXlt
7qRE0OayltSFHaw/jA5O1EupcSILLOcgVjNT9kGqmQMrZeWASVqPpoUaH5BeJF0B
86NuS4GgjYzFQpNUpayZwx81VR1dgNPGKr0AzVyvAvGRRENI5UPoXPsZH9Q/xFu6
r9E6OP14IGVwToOFoJwNAyrMhnB39duomz4e6sNqU3LpT5BjGjXtiMVI2DbEogog
t2aLN9MLBsUsjgfE7v3EnIiYHkYGpVJYlgGBefq0xT6kPt98JclDxqoj9hJiLLmi
rYJ5z9fR9qWfdwfmUROMw4cZlE2pOw==
=PO7o
-----END PGP SIGNATURE-----

--werduicoa52qw56n--