From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Grant Likely <grant.likely@secretlab.ca>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
devicetree-discuss <devicetree-discuss@lists.ozlabs.org>,
Rob Herring <rob.herring@calxeda.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
"David S. Miller" <davem@davemloft.net>
Subject: Re: [PATCH 2/2] of: remove /proc/device-tree
Date: Thu, 21 Mar 2013 05:19:54 +0100 [thread overview]
Message-ID: <1363839594.17680.19.camel@pasglop> (raw)
In-Reply-To: <CACxGe6u2wNbPQSOPRCRO0To5UC-b8rXYanv2xv26hk5oaozvPA@mail.gmail.com>
On Wed, 2013-03-20 at 21:38 +0000, Grant Likely wrote:
> > NAK. It should at the very least be a CONFIG option for a while
> before
> > completely switching over.
>
> I'll modify patch 1 to create the symlink if CONFIG_PROC_DEVICETREE is
> not set. After the first patch can be applied we can leave it for a
> release or two before applying the second.
Shouldn't we have the symlink just be a config option itself ?
Eventually distros might want get rid of it completely ..
Ben.
next prev parent reply other threads:[~2013-03-21 4:20 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 [this message]
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
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=1363839594.17680.19.camel@pasglop \
--to=benh@kernel.crashing.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 \
/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).