From: "Antonin Godard" <antonin.godard@bootlin.com>
To: "Sverdlin, Alexander" <alexander.sverdlin@siemens.com>,
"ejo@pengutronix.de" <ejo@pengutronix.de>,
"docs@lists.yoctoproject.org" <docs@lists.yoctoproject.org>
Cc: "yocto@pengutronix.de" <yocto@pengutronix.de>,
"thomas.petazzoni@bootlin.com" <thomas.petazzoni@bootlin.com>
Subject: Re: [docs] [PATCH v2 12/12] migration-guides/release-notes-5.2: update for upcoming 5.2 release
Date: Thu, 22 May 2025 11:46:06 +0200 [thread overview]
Message-ID: <DA2LDN8GA216.7WD86WP3ZP2W@bootlin.com> (raw)
In-Reply-To: <19948ea8255497b0c3979364e4e7c485695863d2.camel@siemens.com>
On Thu May 15, 2025 at 2:33 PM CEST, Alexander Sverdlin wrote:
> Hi Enrico!
>
> On Mon, 2025-04-14 at 13:12 +0200, Enrico Jörns wrote:
>> > - - ``bluez``: fix mesh build when building with musl.
>> > + - ``systemd``:
>> > +
>> > + - set better sane time at startup by creating the ``clock-epoch`` file in
>> > + ``${libdir}`` if the ``set-time-epoch`` :term:`PACKAGECONFIG` config is
>> > + set.
>> > +
>> > + - really disable Predictable Network Interface names if the ``pni-names``
>> > + feature is not part of :term:`DISTRO_FEATURES`. Previously it was only
>> > + really disable for QEMU machines.
>>
>> ( s/disable/disabled/ )
>>
>> Quick question: My understanding (and observation) is that not having 'pni-names' set in
>> DISTRO_FEATURES (which will be the default for almost everyone) will change the network naming to
>> 'non predictable' now, correct?
>> For me, this is quite unexpected and requires me to add 'pni-name' to keep the original behavior.
>> Shouldn't we then at least add this as a hint to the migration notes?
>
> Thanks for pointing this out!
> I'm sorry this came as a surprise! The reason I didn't think about
> preserving the legacy behaviour is that the behaviour itself was inconsistent (QEMU vs the rest).
>
> Do you think we should add "pni-names" to the default systemd PACKAGECONFIG now as a follow-up patch?
Hi Alexander,
I don't have a strong opinion on this, but I think the best way to get an answer
to that question is to send the patch on OE-Core and wait for feedback, as you
won't get much traction on the docs list. :)
Thanks,
Antonin
--
Antonin Godard, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
prev parent reply other threads:[~2025-05-22 9:46 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-25 9:20 [PATCH v2 00/12] Updates for upcoming 5.2 release Antonin Godard
2025-03-25 9:20 ` [PATCH v2 01/12] ref-manual/classes.rst: document the ptest-python-pytest class and variables Antonin Godard
2025-03-28 13:58 ` [docs] " Quentin Schulz
2025-04-03 13:35 ` Antonin Godard
2025-03-25 9:20 ` [PATCH v2 02/12] ref-manual/variables.rst: WATCHDOG_TIMEOUT: fix recipe name Antonin Godard
2025-03-28 14:00 ` [docs] " Quentin Schulz
2025-03-25 9:20 ` [PATCH v2 03/12] ref-manual/variables.rst: document the WATCHDOG_RUNTIME_SEC variable Antonin Godard
2025-03-28 14:05 ` [docs] " Quentin Schulz
2025-03-25 9:20 ` [PATCH v2 04/12] ref-manual/variables.rst: document the MOUNT_GROUP variable Antonin Godard
2025-03-25 9:20 ` [PATCH v2 05/12] ref-manual/features.rst: drop ld-is-gold Antonin Godard
2025-03-25 9:20 ` [PATCH v2 06/12] ref-manual/variables.rst: document the MESON_INSTALL_TAGS Antonin Godard
2025-03-28 14:08 ` [docs] " Quentin Schulz
2025-03-25 9:20 ` [PATCH v2 07/12] ref-manual/variables.rst: document the NVD_DB_VERSION variable Antonin Godard
2025-03-25 9:20 ` [PATCH v2 08/12] ref-manual/variables.rst: document autotools class related variables Antonin Godard
2025-03-28 14:12 ` [docs] " Quentin Schulz
2025-03-25 9:20 ` [PATCH v2 09/12] migration-guides/migration-5.2.rst: add information about autotools changes Antonin Godard
2025-03-25 9:20 ` [PATCH v2 10/12] ref-manual/variables.rst: add a link for BB_USE_HOME_NPMRC Antonin Godard
2025-03-25 9:20 ` [PATCH v2 11/12] migration-guides/migration-5.2: update for upcoming 5.2 release Antonin Godard
2025-03-28 14:16 ` [docs] " Quentin Schulz
2025-03-25 9:20 ` [PATCH v2 12/12] migration-guides/release-notes-5.2: " Antonin Godard
2025-04-14 11:12 ` [docs] " Enrico Jörns
2025-04-15 12:10 ` Antonin Godard
[not found] ` <19948ea8255497b0c3979364e4e7c485695863d2.camel@siemens.com>
2025-05-22 9:46 ` Antonin Godard [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=DA2LDN8GA216.7WD86WP3ZP2W@bootlin.com \
--to=antonin.godard@bootlin.com \
--cc=alexander.sverdlin@siemens.com \
--cc=docs@lists.yoctoproject.org \
--cc=ejo@pengutronix.de \
--cc=thomas.petazzoni@bootlin.com \
--cc=yocto@pengutronix.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.