From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/2] Refactoring Freescale's iMX software revision levels
Date: Fri, 3 May 2013 19:29:09 +0200 [thread overview]
Message-ID: <20130503192909.716e75a3@skate> (raw)
In-Reply-To: <42565.217.149.209.147.1367582464.squirrel@webmail.internl.net>
Dear H.Fijnvandraat at inter.nl.net,
On Fri, 3 May 2013 14:01:04 +0200 (CEST), H.Fijnvandraat at inter.nl.net
wrote:
> But I have to withdraw these patches.
>
> Due to the sequence in which the .mk files are included
> IMX_VERSION_LEVEL is defined when imx-lib.mk is processed, while it
> is already needed for firmware-imx (and gpu-viv-bin-mx6q if it would
> be introduced)
>
> Placing it in firmware-imx would do for now, but then no dependencies
> can be placed alphabetically before it later.
>
> It appears we need some other mechanism to rule them all.
This shouldn't matter because we're using '=' everywhere, so they are
recursively expanded, which means that the values are expanded only
when the value is actually needed. So the inclusion order shouldn't
matter.
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
prev parent reply other threads:[~2013-05-03 17:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-03 8:27 [Buildroot] [PATCH 1/2] Refactoring Freescale's iMX software revision levels Henk Fijnvandraat
2013-05-03 8:27 ` [Buildroot] [PATCH 2/2] firmware-imx-version: bump to version 1.1.0 Henk Fijnvandraat
2013-05-03 12:01 ` [Buildroot] [PATCH 1/2] Refactoring Freescale's iMX software revision levels H.Fijnvandraat at inter.nl.net
2013-05-03 17:13 ` Arnout Vandecappelle
2013-05-05 19:41 ` Peter Korsgaard
2013-05-03 17:29 ` Thomas Petazzoni [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=20130503192909.716e75a3@skate \
--to=thomas.petazzoni@free-electrons.com \
--cc=buildroot@busybox.net \
/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