From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2] ARM: remove name from machine_desc for DT platforms
Date: Mon, 18 Nov 2013 13:54:39 +0000 [thread overview]
Message-ID: <20131118135439.GC16735@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <CACxGe6sgRwiakJLUCtaaQ2NF51PpkoNZvZr6EoE-BPeZiDsDFQ@mail.gmail.com>
On Fri, Nov 15, 2013 at 02:16:29AM +0900, Grant Likely wrote:
> On Thu, Nov 14, 2013 at 11:46 PM, Rob Herring <robherring2@gmail.com> wrote:
> > If this is a required feature then we should make machine_desc common
> > (or at least part of it) with the other arches that have copied arm and
> > then add it to arm64 as well. Then I could do further consolidation of
> > the FDT machine matching code. Otherwise this is all just pointless
> > architecture variation that really has nothing to do with the architecture.
>
> I think you are missing my point. go ahead, take it out of
> /proc/cpuinfo. That's not the issue.
You do realise this is a user API issue, right?
http://fossies.org/dox/glibc-2.18/ports_2sysdeps_2unix_2sysv_2linux_2arm_2ioperm_8c_source.html
Right, it only has four strings which it matches against, but this is
evidence that /proc/cpuinfo is a user API, and the strings therein are
used by userspace in ways you don't expect.
We can't just go around removing things.
next prev parent reply other threads:[~2013-11-18 13:54 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-03 20:50 [PATCH v2] ARM: remove name from machine_desc for DT platforms Rob Herring
[not found] ` < CAOesGMg7Mt+p8U7Z5sLQDqoFG-QEUi94Vt=pxXM0NqyefBLxVA@mail.gmail.com>
2013-11-04 11:36 ` Grant Likely
2013-11-05 14:34 ` Rob Herring
2013-11-05 17:44 ` Matt Sealey
2013-11-11 17:38 ` Olof Johansson
2013-11-13 19:00 ` Rob Herring
2013-11-13 19:21 ` Olof Johansson
2013-11-13 20:04 ` Rob Herring
2013-11-14 12:32 ` Arnd Bergmann
[not found] ` < CACxGe6uMWjfmB4WDKs+vu05224jqpbDZBHT_ZXnqxw17JzUqvw@mail.gmail.com>
[not found] ` < 5284E236.1000606@gmail.com>
[not found] ` < CACxGe6sgRwiakJLUCtaaQ2NF51PpkoNZvZr6EoE-BPeZiDsDFQ@mail.gmail.com>
2013-11-14 13:33 ` Grant Likely
2013-11-14 14:46 ` Rob Herring
2013-11-14 17:16 ` Grant Likely
2013-11-14 23:17 ` Rob Herring
2013-11-18 12:59 ` Grant Likely
2013-11-18 13:54 ` Russell King - ARM Linux [this message]
2013-11-19 13:43 ` Grant Likely
2013-11-21 23:53 ` Rob Herring
2013-11-15 19:13 ` Russell King - ARM Linux
2013-11-15 20:16 ` Rob Herring
2013-11-15 21:05 ` Arnd Bergmann
2013-11-14 20:33 ` Matt Sealey
2013-11-15 16:08 ` Rob Herring
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=20131118135439.GC16735@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--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;
as well as URLs for NNTP newsgroup(s).