From: cedric_hombourger@mentor.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 00:04:00 -0700 (PDT) [thread overview]
Message-ID: <579a7c07-ffe8-4b5f-b725-dafd315f1ba9@googlegroups.com> (raw)
In-Reply-To: <c8d67591-a529-dd50-8ad6-be2f90f9de77@siemens.com>
[-- Attachment #1.1: Type: text/plain, Size: 1142 bytes --]
On Monday, March 23, 2020 at 4:43:22 PM UTC+1, Jan Kiszka wrote:
>
> On 07.02.20 20:01, [ext] Jan Kiszka wrote:
> > From: Quirin Gylstorff <quirin....@siemens.com <javascript:>>
> >
> > Signed-off-by: Quirin Gylstorff <quirin....@siemens.com <javascript:>>
> > ---
> > meta/recipes-kernel/linux/linux-custom.inc | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/meta/recipes-kernel/linux/linux-custom.inc
> b/meta/recipes-kernel/linux/linux-custom.inc
> > index d31da3b..4fb7ca2 100644
> > --- 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 ??= ""
>
ack. let's get this change in
>
> > # Add our template meta-data to the sources
> > FILESEXTRAPATHS_prepend := "${FILE_DIRNAME}/files:"
> >
>
> Ping. This tiny one seems to have fallen through the cracks.
>
> Jan
>
> --
> Siemens AG, Corporate Technology, CT RDA IOT SES-DE
> Corporate Competence Center Embedded Linux
>
[-- Attachment #1.2: Type: text/html, Size: 2085 bytes --]
next prev parent reply other threads:[~2020-03-25 7:04 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 [this message]
2020-03-25 11:19 ` Baurzhan Ismagulov
2020-03-25 11:33 ` Jan Kiszka
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=579a7c07-ffe8-4b5f-b725-dafd315f1ba9@googlegroups.com \
--to=cedric_hombourger@mentor.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