From: Jan Kiszka <jan.kiszka@siemens.com>
To: isar-users <isar-users@googlegroups.com>
Subject: Re: [PATCH] recipes-kernel/linux: Weaker KERNEL_DEFCONFIG to allow overwrites
Date: Wed, 25 Mar 2020 12:33:19 +0100 [thread overview]
Message-ID: <00c9fafb-7e0e-1da6-f27e-80bcb7db4919@siemens.com> (raw)
In-Reply-To: <20200325111926.y6tuuym3btir25gc@yssyq.m.ilbers.de>
On 25.03.20 12:19, Baurzhan Ismagulov wrote:
> Hello Jan,
>
> On Mon, Mar 23, 2020 at 04:43:21PM +0100, Jan Kiszka wrote:
>>> --- a/meta/recipes-kernel/linux/linux-custom.inc
>>> +++ b/meta/recipes-kernel/linux/linux-custom.inc
>>> @@ -39,7 +39,7 @@ KERNEL_LIBC_DEV_DEPLOY ?= "0"
>>> LINUX_VERSION_EXTENSION ?= ""
>>> -KERNEL_DEFCONFIG ?= ""
>>> +KERNEL_DEFCONFIG ??= ""
>>> # Add our template meta-data to the sources
>>> FILESEXTRAPATHS_prepend := "${FILE_DIRNAME}/files:"
>>
>> Ping. This tiny one seems to have fallen through the cracks.
>
> Not exactly fallen, it was an attempt to postpone the stuff chronologically to
> merge base-apt rework. I'm afraid I have to resume merging ATM. Applied to
> next, thanks for your patience.
Delaying smaller series or individual patches really only make sense
when there are obvious dependency risks. Otherwise, completely unrelated
bug fixes wait too long as well (like "meta: linux-custom: Remove
duplicate and wrong default build dependency" or "sshd-regen-keys: fix
race condition" or likely more).
Jan
--
Siemens AG, Corporate Technology, CT RDA IOT SES-DE
Corporate Competence Center Embedded Linux
next prev parent reply other threads:[~2020-03-25 11:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-07 19:01 Jan Kiszka
2020-03-23 15:43 ` Jan Kiszka
2020-03-25 7:04 ` cedric_hombourger
2020-03-25 11:19 ` Baurzhan Ismagulov
2020-03-25 11:33 ` Jan Kiszka [this message]
2020-03-25 11:34 ` 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=00c9fafb-7e0e-1da6-f27e-80bcb7db4919@siemens.com \
--to=jan.kiszka@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