public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: mark.rutland@arm.com (Mark Rutland)
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:15:26 +0100	[thread overview]
Message-ID: <20170926131525.GE15480@leverpostej> (raw)
In-Reply-To: <20170926124536.GA11192@arm.com>

Hi,

On Tue, Sep 26, 2017 at 01:45:37PM +0100, 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")

> 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.

Seconded.

Experience with the existing /proc/cpuinfo shows that this needs *very*
careful review.

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.

Thanks,
Mark.

  parent reply	other threads:[~2017-09-26 13:15 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
2017-09-26 13:15 ` Mark Rutland [this message]
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=20170926131525.GE15480@leverpostej \
    --to=mark.rutland@arm.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