From: Alexander Aring <alex.aring@gmail.com>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] [PATCH v2 1/2] dtc: Seperate path and filename of dts
Date: Thu, 15 May 2014 11:38:47 +0200 [thread overview]
Message-ID: <20140515093845.GA17528@omega> (raw)
In-Reply-To: <1400145009-4662-1-git-send-email-t.gamez@phytec.de>
On Thu, May 15, 2014 at 11:10:08AM +0200, Teresa Gámez wrote:
> Creating multiple device trees result in a quite
> long DTC_OFTREE_DTS variable. Splitting it into a
> path variable and file variable makes it more handy.
>
> Signed-off-by: Teresa Gámez <t.gamez@phytec.de>
> ---
> Changed v2:
> - Add default for DTC_OFFTREE_DTS_PATH
>
> platforms/dtc.in | 8 +++++++-
> rules/post/dts.make | 8 ++++++--
> 2 files changed, 13 insertions(+), 3 deletions(-)
>
> diff --git a/platforms/dtc.in b/platforms/dtc.in
> index a39af97..dbf3c55 100644
> --- a/platforms/dtc.in
> +++ b/platforms/dtc.in
> @@ -19,9 +19,15 @@ config DTC_INSTALL_OFTREE
> Creates an package to install the 'oftree' file to /boot
> of your target system.
>
> +config DTC_OFTREE_DTS_PATH
> + string "path to source dts file"
> + default "${KERNEL_DIR}/arch/${PTXCONF_KERNEL_ARCH_STRING}/boot/dts/"
little nitpick here. This produce an output of "/foo/bar/boot/dts//bar.foo".
^^
this will not generate a nice output
Sorry, I said in my previous mail
"${KERNEL_DIR}/arch/${PTXCONF_KERNEL_ARCH_STRING}/boot/dts/"... but I
was a little bit too fast and did not remove the '/'. :-(
- Alex
--
ptxdist mailing list
ptxdist@pengutronix.de
next prev parent reply other threads:[~2014-05-15 9:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-15 9:10 Teresa Gámez
2014-05-15 9:10 ` [ptxdist] [PATCH v2 2/2] barebox_mlo: use images/barebox-*-mlo.img as images Teresa Gámez
2014-06-11 6:30 ` Michael Olbrich
2014-05-15 9:38 ` Alexander Aring [this message]
2014-05-16 6:45 ` [ptxdist] [PATCH v2 1/2] dtc: Seperate path and filename of dts Alexander Aring
2014-06-11 6:29 ` Michael Olbrich
2014-06-20 7:23 ` Alexander Aring
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=20140515093845.GA17528@omega \
--to=alex.aring@gmail.com \
--cc=ptxdist@pengutronix.de \
/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