From: Baurzhan Ismagulov <ibr@radix50.net>
To: isar-users@googlegroups.com
Subject: Re: [URGENT PATCH] multiconfig: update stretch kernel versions
Date: Fri, 13 Oct 2017 18:21:54 +0200 [thread overview]
Message-ID: <20171013162154.GD5147@yssyq.radix50.net> (raw)
In-Reply-To: <de323853-f074-a63b-c9fc-6ef003d62b95@siemens.com>
On Fri, Oct 13, 2017 at 05:54:49PM +0200, Jan Kiszka wrote:
> BTW: One version change, but up to three lines modified per variant.
> Wouldn't it make sense to use one variable here?
Bitbake seems to support var expansion in var assignment, so this should be
possible.
As Alex mentioned, there is a better fix:
https://github.com/ilbers/isar/commit/52b8d3563568f1245eea2d74b366f24e94207c56
It determines the version automatically. We'll rebase it and send to the list.
We might still need your suggestion for the following cases:
* Multiple versions in Debian.
* Additional kernels in product repos.
* Kernel not installed into the rootfs.
* No initrd.
With kind regards,
Baurzhan.
next prev parent reply other threads:[~2017-10-13 16:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-13 11:18 Henning Schild
2017-10-13 11:20 ` Jan Kiszka
2017-10-13 11:20 ` Henning Schild
2017-10-13 11:42 ` [URGENT PATCHv2] " Henning Schild
2017-10-13 14:37 ` Baurzhan Ismagulov
2017-10-13 15:54 ` [URGENT PATCH] " Jan Kiszka
2017-10-13 16:21 ` Baurzhan Ismagulov [this message]
2017-10-16 8:04 ` Henning Schild
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=20171013162154.GD5147@yssyq.radix50.net \
--to=ibr@radix50.net \
--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