Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Mikko Rapeli <mikko.rapeli@linaro.org>
To: bruce.ashfield@gmail.com
Cc: richard.purdie@linuxfoundation.org,
	openembedded-core@lists.openembedded.org, ross.burton@arm.com
Subject: Re: [PATCH 0/4] kernel-yocto: 6.16 fixups and genericarm64
Date: Wed, 10 Sep 2025 16:26:38 +0300	[thread overview]
Message-ID: <aMF8jgdGtg6M0TAj@nuoska> (raw)
In-Reply-To: <20250910050822.3273330-1-bruce.ashfield@gmail.com>

Hi,

I missed "poky: bump default kernel reference to 6.16" from
emails and can't find from list archives, but it's leaving
"poky-altcfg" distro with 6.12 kernel. Is this the plan?

When building "poky-altcfg" distro, the machines can't override
kernel version. I would like to see genericarm64 systemd
builds, e.g. "poky-altcfg" distro with the new kernel.

Plain old "poky" sysvinit without systemd, udev etc is hard
to support on broad range of HW. Thus I am testing genericarm64
with "poky-altcfg", which can't easily update to 6.16 kernel,
at least without https://lists.yoctoproject.org/g/poky/message/13742

Cheers,

-Mikko


  parent reply	other threads:[~2025-09-10 13:26 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-10  5:08 [PATCH 0/4] kernel-yocto: 6.16 fixups and genericarm64 bruce.ashfield
2025-09-10  5:08 ` [PATCH 1/4] linux-yocto/6.16: cfg: DRM tweaks for guests bruce.ashfield
2025-09-10  5:08 ` [PATCH 2/4] linux-yocto/6.16: cfg: x86 BIGSMP removal bruce.ashfield
2025-09-10  5:08 ` [PATCH 3/4] yocto-bsp: introduce 6.16 bbappend bruce.ashfield
2025-09-10  5:17   ` Patchtest results for " patchtest
2025-09-10  5:08 ` [PATCH 4/4] linux-yocto/6.16: genericarm64 config bruce.ashfield
2025-09-10 11:16 ` [PATCH 0/4] kernel-yocto: 6.16 fixups and genericarm64 Richard Purdie
2025-09-10 12:56   ` Bruce Ashfield
2025-09-10 12:58     ` Richard Purdie
2025-09-10 13:26 ` Mikko Rapeli [this message]
2025-09-10 13:28   ` Richard Purdie
2025-09-10 13:40     ` Mikko Rapeli

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=aMF8jgdGtg6M0TAj@nuoska \
    --to=mikko.rapeli@linaro.org \
    --cc=bruce.ashfield@gmail.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=richard.purdie@linuxfoundation.org \
    --cc=ross.burton@arm.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