From: Max Krummenacher <max.oss.09@gmail.com>
To: Otavio Salvador <otavio.salvador@ossystems.com.br>,
Maciej Borzecki <maciej.borzecki@rndity.com>
Cc: "meta-freescale@yoctoproject.org"
<meta-freescale@yoctoproject.org>,
Stefan Agner <stefan.agner@toradex.com>
Subject: Re: [3rdparty][PATCH] u-boot-toradex: add dependency on dtc-native
Date: Tue, 25 Jul 2017 22:02:18 +0200 [thread overview]
Message-ID: <1501012938.3127.9.camel@gmail.com> (raw)
In-Reply-To: <CAP9ODKqwe+DAFkiVsk0vJL77=gbett-ect6cohMwGFgT+WfdDw@mail.gmail.com>
Hi
Am Dienstag, den 25.07.2017, 10:27 -0300 schrieb Otavio Salvador:
> On Tue, Jul 25, 2017 at 9:49 AM, Maciej Borzecki
> <maciej.borzecki@rndity.com> wrote:
> > The recipes-bsp/u-boot/u-boot-toradex.inc is included by u-boot-toradex recipes
> > in meta-toradex-nxp as well. Add dependency on dtc-native as it will be required
> > to build 2016.11 release, which may eventually hit meta-freescale-3rdparty
> > tree too.
> >
> > Signed-off-by: Maciej Borzecki <maciej.borzecki@rndity.com>
>
> I'd prefer if you send the bump so it is actually used.
I'm actually in the process of updating all our machines, U-Boot and kernel
recipes, including going to 2016.11 with U-Boot.
I already added the dependency on dtc-native in my patch-set, so it will be there
when we update to 2016.11. (or I will rebase should this patch get merged).
Testing will however take some more time as I want this to work with poky and angstrom
and with and without our downstream meta-toradex-xxx layers.
Max
>
> --
> Otavio Salvador O.S. Systems
> http://www.ossystems.com.br http://code.ossystems.com.br
> Mobile: +55 (53) 9981-7854 Mobile: +1 (347) 903-9750
next prev parent reply other threads:[~2017-07-25 20:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-25 12:49 [3rdparty][PATCH] u-boot-toradex: add dependency on dtc-native Maciej Borzecki
2017-07-25 13:27 ` Otavio Salvador
2017-07-25 20:02 ` Max Krummenacher [this message]
2017-08-01 7:16 ` Maciej Borzęcki
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=1501012938.3127.9.camel@gmail.com \
--to=max.oss.09@gmail.com \
--cc=maciej.borzecki@rndity.com \
--cc=meta-freescale@yoctoproject.org \
--cc=otavio.salvador@ossystems.com.br \
--cc=stefan.agner@toradex.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 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.