From: Anton Mikanovich <amikan@ilbers.de>
To: Srinuvasan A <Srinuvasan_A@mentor.com>, isar-users@googlegroups.com
Cc: jan.kiszka@siemens.com
Subject: Re: [PATCH] bitbake.conf: Add BASE_DISTRO_CODENAME in OVERRIDES variable
Date: Wed, 28 Sep 2022 12:22:33 +0300 [thread overview]
Message-ID: <ec8ce91c-6b6c-18d3-0351-1be8811213bb@ilbers.de> (raw)
In-Reply-To: <20220923102855.1357346-1-Srinuvasan_A@mentor.com>
23.09.2022 13:28, Srinuvasan A wrote:
> From: Srinuvasan A <srinuvasan_a@mentor.com>
>
> Commit 4ffdf792 says, Switch custom kernel modules to use libssl3 by
> default and left libssl1.1 dependency only for distros not yet
> migrated, here they used overrides based on "DISTRO".
>
> Here DISTRO is debian-bullseye or debian-buster and so on, downstream layers might define
> their own DISTRO name.
>
> Use the overrides based on "BASE_DISTRO_CODENAME" to pick up the exact version of libssl
> for the corresponding DISTRO to better support downstream layers with custom DISTRO names.
>
> Signed-off-by: Srinuvasan A <srinuvasan_a@mentor.com>
Applied to next, thanks.
prev parent reply other threads:[~2022-09-28 9:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <AQHYzzdafU+zAaufNESZAMqViN9X/63vz2pQ>
2022-09-22 6:19 ` [PATCH] linux-custom: Update to BASE_DISTRO_CODENAME instead of DISTRO Srinuvasan A
2022-09-23 9:33 ` Anton Mikanovich
2022-09-23 10:28 ` [PATCH] bitbake.conf: Add BASE_DISTRO_CODENAME in OVERRIDES variable Srinuvasan A
2022-09-25 8:27 ` Moessbauer, Felix
2022-09-26 9:55 ` Srinuvasan Arjunan
2022-09-26 10:03 ` Anton Mikanovich
2022-09-28 9:22 ` Anton Mikanovich [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=ec8ce91c-6b6c-18d3-0351-1be8811213bb@ilbers.de \
--to=amikan@ilbers.de \
--cc=Srinuvasan_A@mentor.com \
--cc=isar-users@googlegroups.com \
--cc=jan.kiszka@siemens.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