From: Peter Kjellerstedt <peter.kjellerstedt@axis.com>
To: Markus Niebel <Markus.Niebel@ew.tq-group.com>,
"openembedded-core@lists.openembedded.org"
<openembedded-core@lists.openembedded.org>
Subject: RE: [OE-core] bitbake.conf: reason for assignment of deprecated variable
Date: Fri, 15 Apr 2022 00:08:04 +0000 [thread overview]
Message-ID: <5b5b2b45fe494472abcfc8e06c6480c2@axis.com> (raw)
In-Reply-To: <2d083c9ebada9a9ee8eaf9c97f3ef3171bdb2356.camel@ew.tq-group.com>
> -----Original Message-----
> From: openembedded-core@lists.openembedded.org <openembedded-
> core@lists.openembedded.org> On Behalf Of Markus Niebel
> Sent: den 11 april 2022 17:07
> To: openembedded-core@lists.openembedded.org
> Subject: [OE-core] bitbake.conf: reason for assignment of deprecated
> variable
>
> Hello,
>
> with the deprecation of SERIAL_CONSOLE the following was introduced in
> bitbake.conf:
>
> 3f0d665384e6d1b7aa2854a9cc4f13e0961bacb7 (bitbake.conf: set
> SERIAL_CONSOLES from SERIAL_CONSOLE by default)
>
> Since this is done after inclusion of local.conf and <machine>.conf any
> weak default done for a System-on-Module / CPU will be overwritten. Is
> this just by forgetting to remove these lines after the deprecation or
> is there still a reason to keep this as is?
>
> Thank you
>
> Markus Niebel
Given that it is almost ten years since SERIAL_CONSOLE was deprecated,
it might be time to actually remove it soon...
//Peter
next prev parent reply other threads:[~2022-04-18 14:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-11 15:06 bitbake.conf: reason for assignment of deprecated variable Markus Niebel
2022-04-15 0:08 ` Peter Kjellerstedt [this message]
2022-04-15 10:02 ` [OE-core] " Michael Opdenacker
2022-04-15 11:54 ` Richard Purdie
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=5b5b2b45fe494472abcfc8e06c6480c2@axis.com \
--to=peter.kjellerstedt@axis.com \
--cc=Markus.Niebel@ew.tq-group.com \
--cc=openembedded-core@lists.openembedded.org \
/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