public inbox for poky@lists.yoctoproject.org
 help / color / mirror / Atom feed
From: Mikko Rapeli <mikko.rapeli@linaro.org>
To: Bruce Ashfield <bruce.ashfield@gmail.com>
Cc: openembedded-core@lists.openembedded.org, poky@lists.yoctoproject.org
Subject: Re: [poky] [PATCH 2/3] kernel-yocto.bbclass: support modular kernel configs
Date: Wed, 23 Apr 2025 15:40:52 +0300	[thread overview]
Message-ID: <aAjf1EfWpWQt_RZ2@nuoska> (raw)
In-Reply-To: <CADkTA4OM83dmNKO-ocCRmoVzaMWCxvN0SYz7Yi3th58uPoSqHw@mail.gmail.com> <CADkTA4PjYn55Udo7KxJwQi_SK08r+a_6EwMyo=e1-Y1vDKtxYA@mail.gmail.com> <CADkTA4MUkWtgpj=FG2rGN+kHQqkGLWjLPMDiyBi3TUct+Th4EQ@mail.gmail.com>

Hi,

On Wed, Apr 23, 2025 at 08:30:50AM -0400, Bruce Ashfield wrote:
> I already have patches for this, and they have not been sent on purpose.
> 
> Please do not apply this patch, consider this a nack.

Ok, no worries.

If you have the draft patches somewhere I can try them out on genericarm64
builds and test on a few devices, if that helps.

genericarm64 core-image-initramfs-boot is exceeding size limits currently
so I wanted to publish what I had already:

https://bugzilla.yoctoproject.org/show_bug.cgi?id=15833

Cheers,

-Mikko


  reply	other threads:[~2025-04-23 12:41 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-23  8:02 [PATCH 1/3] kern-tools-native: update to support modular kernel builds Mikko Rapeli
2025-04-23  8:02 ` [PATCH 2/3] kernel-yocto.bbclass: support modular kernel configs Mikko Rapeli
2025-04-23 12:30   ` [poky] " Bruce Ashfield
2025-04-23 12:40     ` Mikko Rapeli [this message]
2025-04-23  8:02 ` [PATCH 3/3] linux-yocto: build modular kernel on genericarm64 Mikko Rapeli
2025-04-23 12:31   ` [OE-core] " Bruce Ashfield
2025-04-23 12:31 ` [poky] [PATCH 1/3] kern-tools-native: update to support modular kernel builds Bruce Ashfield

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=aAjf1EfWpWQt_RZ2@nuoska \
    --to=mikko.rapeli@linaro.org \
    --cc=bruce.ashfield@gmail.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=poky@lists.yoctoproject.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