public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Pankaj Dubey <pankaj.dubey@samsung.com>
To: Liviu Dudau <Liviu.Dudau@arm.com>,
	arm@kernel.org, Olof Johansson <olof@lixom.net>,
	Arnd Bergmann <arnd@arndb.de>, Kevin Hilman <khilman@linaro.org>
Cc: Mark Rutland <mark.rutland@arm.com>,
	device tree <devicetree@vger.kernel.org>,
	Pawel Moll <pawel.moll@arm.com>,
	Ian Campbell <ijc+devicetree@hellion.org.uk>,
	Catalin Marinas <catalin.marinas@arm.com>,
	Will Deacon <will.deacon@arm.com>,
	LKML <linux-kernel@vger.kernel.org>,
	Rob Herring <robh+dt@kernel.org>,
	Kumar Gala <galak@codeaurora.org>,
	LAKML <linux-arm-kernel@lists.infradead.org>
Subject: Re: [v3, 1/2] arm64: Create link to include/dt-bindings to enable C preprocessor use.
Date: Thu, 27 Nov 2014 14:04:29 +0530	[thread overview]
Message-ID: <5476E215.5020405@samsung.com> (raw)
In-Reply-To: <1415727131-4572-2-git-send-email-Liviu.Dudau@arm.com>

Hi Liviu,

On Tuesday 11 November 2014 11:02 PM, Liviu Dudau wrote:
> DT files used in the compilation phase can be preprocessed by the C
> preprocessor. This requires an include/dt-bindings directory to be
> present in the arch/arm64/boot/dts directory.
>
> Signed-off-by: Liviu Dudau <Liviu.Dudau@arm.com>
>

Same change already has been posted as part of adding Exynos7 SoC 
support, as Exynos7 patches have been accepted in Kukjin's tree, I think 
following patch [1] as part of Exynos7 series [2] can also be taken.

1: http://www.spinics.net/lists/devicetree/msg56552.html
2: http://www.spinics.net/lists/devicetree/msg56551.html

Thanks,
Pankaj Dubey

> ---
> arch/arm64/boot/dts/include/dt-bindings | 1 +
>   1 file changed, 1 insertion(+)
>   create mode 120000 arch/arm64/boot/dts/include/dt-bindings
>
> \ No newline at end of file
>
> diff --git a/arch/arm64/boot/dts/include/dt-bindings b/arch/arm64/boot/dts/include/dt-bindings
> new file mode 120000
> index 0000000..08c00e4
> --- /dev/null
> +++ b/arch/arm64/boot/dts/include/dt-bindings
> @@ -0,0 +1 @@
> +../../../../../include/dt-bindings
>

  reply	other threads:[~2014-11-27  8:34 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-11 17:32 [PATCH v3 0/2] arm64: Add support for Juno development board Liviu Dudau
2014-11-11 17:32 ` [PATCH v3 1/2] arm64: Create link to include/dt-bindings to enable C preprocessor use Liviu Dudau
2014-11-27  8:34   ` Pankaj Dubey [this message]
2014-11-27 11:24     ` [v3, " Liviu Dudau
2014-11-11 17:32 ` [PATCH v3 2/2] arm64: Add Juno board device tree Liviu Dudau
2014-11-26 10:30   ` Marc Zyngier
2014-11-26 10:59     ` Liviu Dudau
2014-11-26 11:36       ` Marc Zyngier
2014-11-20 10:54 ` [PATCH v3 0/2] arm64: Add support for Juno development board Liviu Dudau
2014-11-20 16:52 ` Arnd Bergmann

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=5476E215.5020405@samsung.com \
    --to=pankaj.dubey@samsung.com \
    --cc=Liviu.Dudau@arm.com \
    --cc=arm@kernel.org \
    --cc=arnd@arndb.de \
    --cc=catalin.marinas@arm.com \
    --cc=devicetree@vger.kernel.org \
    --cc=galak@codeaurora.org \
    --cc=ijc+devicetree@hellion.org.uk \
    --cc=khilman@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=olof@lixom.net \
    --cc=pawel.moll@arm.com \
    --cc=robh+dt@kernel.org \
    --cc=will.deacon@arm.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