From: Paul Bolle <pebolle@tiscali.nl>
To: Grant Likely <grant.likely@secretlab.ca>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Rob Herring <rob.herring@linaro.org>
Subject: Re: [git pull] Devicetree changes for v3.15
Date: Tue, 01 Apr 2014 21:42:37 +0200 [thread overview]
Message-ID: <1396381357.23763.16.camel@x220> (raw)
In-Reply-To: <CACxGe6vCrkHPL6UNy1p8AO4+z5VFRY6w4_2grQEZQwp_3jJ7Yw@mail.gmail.com>
On Tue, 2014-04-01 at 11:15 +0100, Grant Likely wrote:
> Grant Likely (13):
> [...]
> of: remove /proc/device-tree
That commit leaves a select for PROC_DEVICETREE dangling. See "config
ARCH_OMAP2PLUS" in arch/arm/mach-omap2/Kconfig. Can that select
statement just be dropped now or is something more elaborate needed?
Paul Bolle
next prev parent reply other threads:[~2014-04-01 19:42 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-01 10:15 Grant Likely
2014-04-01 19:42 ` Paul Bolle [this message]
2014-04-01 20:18 ` Rob Herring
2014-04-01 20:34 ` Paul Bolle
2014-04-01 20:32 ` Grant Likely
2014-04-01 20:39 ` Grant Likely
2014-04-01 20:46 ` Paul Bolle
2014-09-26 12:30 ` Linus Walleij
2014-09-26 14:19 ` Jason Cooper
2014-09-29 8:52 ` Linus Walleij
2014-10-27 15:39 ` Linus Walleij
2014-11-02 20:52 ` [PATCH] ARM: kbuild: Fix forced rebuild after 'make dtbs' Jason Cooper
2014-11-25 21:41 ` Michal Marek
2014-11-25 23:51 ` Russell King - ARM Linux
2014-11-26 0:57 ` Jason Cooper
2014-11-26 13:57 ` Linus Walleij
2014-11-26 14:41 ` Russell King - ARM Linux
2014-11-28 14:10 ` Linus Walleij
2014-12-01 13:55 ` Michal Marek
2014-12-04 11:22 ` Grant Likely
2014-12-04 11:24 ` Russell King - ARM Linux
2014-11-26 9:39 ` Michal Marek
2014-09-29 12:49 ` [git pull] Devicetree changes for v3.15 Grant Likely
2014-09-29 13:52 ` Jason Cooper
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=1396381357.23763.16.camel@x220 \
--to=pebolle@tiscali.nl \
--cc=devicetree@vger.kernel.org \
--cc=grant.likely@secretlab.ca \
--cc=linux-kernel@vger.kernel.org \
--cc=rob.herring@linaro.org \
--cc=torvalds@linux-foundation.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
Powered by JetHome