From: Rob Landley <rob@landley.net>
To: Daniel Mack <daniel@zonque.org>
Cc: Rob Herring <robherring2@gmail.com>,
Grant Likely <grant.likely@secretlab.ca>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
devicetree-discuss@lists.ozlabs.org,
linux-kernel@vger.kernel.org,
Rob Herring <rob.herring@calxeda.com>,
"David S. Miller" <davem@davemloft.net>
Subject: Re: [PATCH 2/2] of: remove /proc/device-tree
Date: Wed, 20 Mar 2013 23:03:39 -0500 [thread overview]
Message-ID: <1363838619.15703.52@driftwood> (raw)
In-Reply-To: <CACTFLAMXHA58bu_c0hRQuZ=nru63hLaixNXaiU-Xa60WD5d=ew@mail.gmail.com> (from daniel@zonque.org on Wed Mar 20 11:24:54 2013)
On 03/20/2013 11:24:54 AM, Daniel Mack wrote:
> On Wed, Mar 20, 2013 at 4:19 PM, Rob Herring <robherring2@gmail.com>
> wrote:
> > On 03/20/2013 09:51 AM, Grant Likely wrote:
> >> The same data is now available in sysfs, so we can remove the code
> >> that exports it in /proc and replace it with a symlink to the sysfs
> >> version.
> >>
> >> Tested on versatile qemu model and mpc5200 eval board. More testing
> >> would be appreciated.
> >
> > I would suggest testing with lshw in particular. That's the only
> > /proc/device-tree user I've come across.
>
> kexec is another one. Not to mention various vendor scripts that
> aren't
> necessarily public.
>
> Don't such things also fall under the "we do not break userspace
> compatibility - ever" rule?
We used to have feature-removal-schedule. Linus removed it. (He did not
add it to feature-removal-schedule first.)
Rob
prev parent reply other threads:[~2013-03-21 4:03 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-20 14:51 [PATCH 0/2] of: Create sysfs view of device tree nodes Grant Likely
2013-03-20 14:51 ` [PATCH 1/2] of: Make device nodes kobjects so they show up in sysfs Grant Likely
2013-03-20 14:57 ` Benjamin Herrenschmidt
2013-03-20 16:56 ` Greg Kroah-Hartman
2013-03-20 17:46 ` Benjamin Herrenschmidt
2013-03-20 21:28 ` Grant Likely
2013-03-20 14:51 ` [PATCH 2/2] of: remove /proc/device-tree Grant Likely
2013-03-20 14:57 ` Benjamin Herrenschmidt
2013-03-20 21:38 ` Grant Likely
2013-03-21 4:19 ` Benjamin Herrenschmidt
2013-03-21 7:35 ` Grant Likely
2013-03-21 7:43 ` Benjamin Herrenschmidt
2013-03-21 8:16 ` Grant Likely
2013-03-21 12:36 ` Benjamin Herrenschmidt
2013-03-21 12:42 ` Grant Likely
2013-11-16 20:09 ` Geert Uytterhoeven
2013-03-20 15:19 ` Rob Herring
2013-03-20 16:24 ` Daniel Mack
2013-03-20 16:40 ` Grant Likely
2013-03-21 4:03 ` Rob Landley [this message]
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=1363838619.15703.52@driftwood \
--to=rob@landley.net \
--cc=daniel@zonque.org \
--cc=davem@davemloft.net \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=grant.likely@secretlab.ca \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rob.herring@calxeda.com \
--cc=robherring2@gmail.com \
/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).