From: Baurzhan Ismagulov <ibr@radix50.net>
To: isar-users <isar-users@googlegroups.com>
Subject: Re: [PATCH] linux-custom: Fix KERNEL_NAME passed into build script
Date: Wed, 19 Jun 2019 12:47:32 +0200 [thread overview]
Message-ID: <20190619104732.GX3977@yssyq.m.ilbers.de> (raw)
In-Reply-To: <cbb17ff2-b907-7d94-e008-e3bf5ab85dce@siemens.com>
On Fri, Jun 14, 2019 at 06:16:00PM +0200, Jan Kiszka wrote:
> We actually have to use the recipe-defined variable KERNEL_NAME_PROVIDED
> here, not the globally defined KERNEL_NAME that selects the
> to-be-installed kernel on an image.
Applied to next, thanks.
With kind regards,
Baurzhan.
prev parent reply other threads:[~2019-06-19 10:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-14 16:16 Jan Kiszka
2019-06-19 10:47 ` Baurzhan Ismagulov [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=20190619104732.GX3977@yssyq.m.ilbers.de \
--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