From: Ralf Baechle <ralf@linux-mips.org>
To: Stephen Warren <swarren@wwwdotorg.org>
Cc: James Hogan <james.hogan@imgtec.com>,
Stephen Warren <swarren@nvidia.com>,
Michal Marek <mmarek@suse.cz>, Shawn Guo <shawn.guo@linaro.org>,
Ian Campbell <ian.campbell@citrix.com>,
Mark Rutland <mark.rutland@arm.com>,
Pawel Moll <pawel.moll@arm.com>,
Rob Herring <rob.herring@calxeda.com>,
linux-mips@linux-mips.org, devicetree@vger.kernel.org,
linux-kbuild@vger.kernel.org
Subject: Re: [PATCH] MIPS: add <dt-bindings/> symlink
Date: Tue, 3 Sep 2013 17:11:58 +0200 [thread overview]
Message-ID: <20130903151158.GB14258@linux-mips.org> (raw)
In-Reply-To: <521505E2.3050308@wwwdotorg.org>
On Wed, Aug 21, 2013 at 12:24:34PM -0600, Stephen Warren wrote:
> On 08/21/2013 08:36 AM, James Hogan wrote:
> > Add symlink to include/dt-bindings from arch/mips/boot/dts/include/ to
> > match the ones in ARM and Meta architectures so that preprocessed device
> > tree files can include various useful constant definitions.
> >
> > See commit c58299a (kbuild: create an "include chroot" for DT bindings)
> > merged in v3.10-rc1 for details.
> >
> > MIPS structures it's dts files a little differently to other
> > architectures, having a separate dts directory for each SoC/platform,
> > but most of the definitions in the dt-bindings/ directory are common so
> > for now lets just have a single "include chroot" for all MIPS platforms.
>
> Acked-by: Stephen Warren <swarren@nvidia.com>
Applied - but I'd be happier if there was a way of achiving the same thing
without symlinks.
Ralf
prev parent reply other threads:[~2013-09-03 15:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-21 14:36 [PATCH] MIPS: add <dt-bindings/> symlink James Hogan
2013-08-21 14:36 ` James Hogan
2013-08-21 18:24 ` Stephen Warren
2013-09-03 15:11 ` Ralf Baechle [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=20130903151158.GB14258@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=devicetree@vger.kernel.org \
--cc=ian.campbell@citrix.com \
--cc=james.hogan@imgtec.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-mips@linux-mips.org \
--cc=mark.rutland@arm.com \
--cc=mmarek@suse.cz \
--cc=pawel.moll@arm.com \
--cc=rob.herring@calxeda.com \
--cc=shawn.guo@linaro.org \
--cc=swarren@nvidia.com \
--cc=swarren@wwwdotorg.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.