From: fschnizlein@suse.com (Felix Schnizlein)
To: linux-arm-kernel@lists.infradead.org
Subject: Unreviewed arm64 ABI change in linux-next via driver-core tree
Date: Tue, 26 Sep 2017 14:57:01 +0200 [thread overview]
Message-ID: <20170926125701.k7hqdt5pbkolkhak@angmar> (raw)
In-Reply-To: <20170926124536.GA11192@arm.com>
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,
>
> We stumbled over a change in linux-next that has ABI implications for arm64
> and, as far as we can tell, has not been reviewed:
>
> https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/arch/arm64/kernel?id=fb7ff3f8721b87bf078868c9a252fa0cf71a47c2
>
> ("fb7ff3f8721b cpuinfo: implement sysfs nodes for arm64")
>
> It looks like this was requested by you on LKML here:
>
> https://lkml.org/lkml/2017/8/2/663
>
> but these sorts of changes really need to go on the linux-arm-kernel mailing
> list with the maintainers on cc so that the patches can be properly reviewed
> 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.
>
> 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 discussion
> started because, aside from this email, we have concerns about exactly what
> is being exposed to userspace here.
>
> Thanks,
>
> Will
>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 488 bytes
Desc: not available
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20170926/cbb9c5f3/attachment.sig>
next prev parent reply other threads:[~2017-09-26 12:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-26 12:45 Unreviewed arm64 ABI change in linux-next via driver-core tree Will Deacon
2017-09-26 12:57 ` Felix Schnizlein [this message]
2017-09-26 13:15 ` Mark Rutland
2017-09-26 13:21 ` Felix Schnizlein
2017-09-26 21:20 ` Greg KH
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20170926125701.k7hqdt5pbkolkhak@angmar \
--to=fschnizlein@suse.com \
--cc=linux-arm-kernel@lists.infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox