From: Jan Kiszka <jan.kiszka@siemens.com>
To: Henning Schild <henning.schild@siemens.com>
Cc: isar-users <isar-users@googlegroups.com>
Subject: Re: [PATCH v2 0/3] u-boot regression fix, cleanup restoration
Date: Mon, 26 Nov 2018 10:49:53 +0100 [thread overview]
Message-ID: <18e2a91e-7117-2be1-973b-5002a0f2ee75@siemens.com> (raw)
In-Reply-To: <20181126104745.0f2c89be@md1za8fc.ad001.siemens.net>
On 26.11.18 10:47, Henning Schild wrote:
> Did you try putting MACHINE into PV and pinning on that? It is always
> the same package and multiple versions are .... multiple versions.
That won't fly. We want recipes to generate results that be be exchanged
(u-boot-myboard either from u-boot mainline or from some vendor recipe).
Jan
>
> Henning
>
> Am Fri, 23 Nov 2018 20:09:44 +0100
> schrieb Jan Kiszka <jan.kiszka@siemens.com>:
>
>> See patches for details.
>>
>> Urgent for downstream layers with multiple custom u-boot recipes.
>>
>> Jan Kiszka (3):
>> Revert "u-boot-custom: Use bitbake variables instead of hardcoded
>> values"
>> meta-isar: u-boot: Encode version in URL via PV
>> u-boot-custom: Add -dev package to PROVIDES
>>
>> meta-isar/recipes-bsp/u-boot/u-boot_2018.09.bb | 2 +-
>> meta/recipes-bsp/u-boot/files/debian/control | 6 +++---
>> meta/recipes-bsp/u-boot/u-boot-custom.inc | 2 +-
>> 3 files changed, 5 insertions(+), 5 deletions(-)
>>
>
--
Siemens AG, Corporate Technology, CT RDA IOT SES-DE
Corporate Competence Center Embedded Linux
next prev parent reply other threads:[~2018-11-26 9:49 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-23 19:09 Jan Kiszka
2018-11-23 19:09 ` [PATCH v2 1/3] Revert "u-boot-custom: Use bitbake variables instead of hardcoded values" Jan Kiszka
2018-11-23 19:09 ` [PATCH v2 2/3] meta-isar: u-boot: Encode version in URL via PV Jan Kiszka
2018-11-23 19:09 ` [PATCH v2 3/3] u-boot-custom: Add -dev package to PROVIDES Jan Kiszka
2018-11-26 9:47 ` [PATCH v2 0/3] u-boot regression fix, cleanup restoration Henning Schild
2018-11-26 9:49 ` Jan Kiszka [this message]
2018-11-26 10:16 ` Henning Schild
2018-11-26 11:08 ` Jan Kiszka
2018-11-26 16:51 ` Henning Schild
2018-11-27 9:55 ` Henning Schild
2018-11-26 13:15 ` Maxim Yu. Osipov
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=18e2a91e-7117-2be1-973b-5002a0f2ee75@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=henning.schild@siemens.com \
--cc=isar-users@googlegroups.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