From: swarren@wwwdotorg•org (Stephen Warren)
To: linux-arm-kernel@lists•infradead.org
Subject: [RFC 1/2] Makefile: Add arch/arch/$(hdr-arch)/boot in header include path
Date: Fri, 15 Feb 2013 09:25:34 -0700 [thread overview]
Message-ID: <511E617E.6080206@wwwdotorg.org> (raw)
In-Reply-To: <1360918364-27960-1-git-send-email-hdoyu@nvidia.com>
On 02/15/2013 01:52 AM, Hiroshi Doyu wrote:
> With a new feature dtc+cpp, DT can introduces some definitions in its
> header files for their own. Some of those DT info can be used in
> kernel source as well, instead of having the duplicate info in kernel
> headers. This patch allows kernel source to include those DT
> headers. For example:
>
> + #include <dts/tegra20-car.h>
Since this is devicetree-related, the DT maintainers should also be
CC'd. I've added them on this email, hence quoting the entire patch.
>
> Signed-off-by: Hiroshi Doyu <hdoyu@nvidia•com>
> ---
> Makefile | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/Makefile b/Makefile
> index 0b4bf62..7f54cdb 100644
> --- a/Makefile
> +++ b/Makefile
> @@ -364,7 +364,7 @@ LINUXINCLUDE := \
> -I$(srctree)/arch/$(hdr-arch)/include \
> -Iarch/$(hdr-arch)/include/generated \
> $(if $(KBUILD_SRC), -I$(srctree)/include) \
> - -Iinclude \
> + -Iinclude -Iarch/$(hdr-arch)/boot \
> $(USERINCLUDE)
>
> KBUILD_CPPFLAGS := -D__KERNEL__
>
next prev parent reply other threads:[~2013-02-15 16:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-15 8:52 [RFC 1/2] Makefile: Add arch/arch/$(hdr-arch)/boot in header include path Hiroshi Doyu
2013-02-15 16:25 ` Stephen Warren [this message]
2013-02-18 13:26 ` Michal Marek
2013-02-19 17:18 ` Stephen Warren
[not found] ` <1360918364-27960-2-git-send-email-hdoyu@nvidia.com>
2013-02-15 16:29 ` [RFC 2/2] clk: tegra20: Use DT defines for CLK ID Stephen Warren
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=511E617E.6080206@wwwdotorg.org \
--to=swarren@wwwdotorg$(echo .)org \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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