From: Ralf Baechle <ralf@linux-mips.org>
To: Rob Herring <robh@kernel.org>
Cc: devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
Grant Likely <grant.likely@linaro.org>,
Benjamin Herrenschmidt <benh@kernel.crashing.org>,
Paul Mackerras <paulus@samba.org>,
Michael Ellerman <mpe@ellerman.id.au>,
linux-mips@linux-mips.org, linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH] of: clean-up unnecessary libfdt include paths
Date: Wed, 3 Jun 2015 10:26:38 +0200 [thread overview]
Message-ID: <20150603082638.GJ9839@linux-mips.org> (raw)
In-Reply-To: <1433308225-13874-1-git-send-email-robh@kernel.org>
On Wed, Jun 03, 2015 at 12:10:25AM -0500, Rob Herring wrote:
> Date: Wed, 3 Jun 2015 00:10:25 -0500
> From: Rob Herring <robh@kernel.org>
> To: devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
> Cc: Grant Likely <grant.likely@linaro.org>, Rob Herring <robh@kernel.org>,
> Ralf Baechle <ralf@linux-mips.org>, Benjamin Herrenschmidt
> <benh@kernel.crashing.org>, Paul Mackerras <paulus@samba.org>, Michael
> Ellerman <mpe@ellerman.id.au>, linux-mips@linux-mips.org,
> linuxppc-dev@lists.ozlabs.org
> Subject: [PATCH] of: clean-up unnecessary libfdt include paths
>
> With the latest dtc import include fixups, it is no longer necessary to
> add explicit include paths to use libfdt. Remove these across the
> kernel.
>
> Signed-off-by: Rob Herring <robh@kernel.org>
> Cc: Ralf Baechle <ralf@linux-mips.org>
> Cc: Benjamin Herrenschmidt <benh@kernel.crashing.org>
> Cc: Paul Mackerras <paulus@samba.org>
> Cc: Michael Ellerman <mpe@ellerman.id.au>
> Cc: Grant Likely <grant.likely@linaro.org>
> Cc: linux-mips@linux-mips.org
> Cc: linuxppc-dev@lists.ozlabs.org
For the MIPS bits;
Acked-by: Ralf Baechle <ralf@linux-mips.org>
Ralf
next prev parent reply other threads:[~2015-06-03 8:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-03 5:10 [PATCH] of: clean-up unnecessary libfdt include paths Rob Herring
2015-06-03 8:26 ` Ralf Baechle [this message]
2015-06-04 8:02 ` Grant Likely
2015-06-04 10:20 ` Michael Ellerman
2015-06-04 10:20 ` Michael Ellerman
2015-06-04 10:20 ` Michael Ellerman
2015-06-04 17:02 ` 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=20150603082638.GJ9839@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=benh@kernel.crashing.org \
--cc=devicetree@vger.kernel.org \
--cc=grant.likely@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@linux-mips.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.au \
--cc=paulus@samba.org \
--cc=robh@kernel.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.