Openembedded Core Discussions
 help / color / mirror / Atom feed
From: "Anusmita Dutta Mazumder" <anusmita.duttamazumder@arm.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 0/5] devtool: Support multiconfig workflows and fix kernel extraction
Date: Thu, 19 Nov 2026 02:24:05 -0800	[thread overview]
Message-ID: <966833.1795083845075041074@lists.openembedded.org> (raw)
In-Reply-To: <2990982.1793200206089623219@lists.openembedded.org>

[-- Attachment #1: Type: text/plain, Size: 480 bytes --]

Hi all,

I’m following up on the workspace design discussion for this devtool multiconfig series. Adrian raised the overlap with his work on supporting multiple recipe variants, and I’ve proposed building the multiconfig support on the relevant shared-workspace changes from his series.

Could the maintainers share their thoughts on this direction and how best to coordinate the two series? That would help me prepare the next revision.

Thanks and regards,
Anusmita

[-- Attachment #2: Type: text/html, Size: 527 bytes --]

      reply	other threads:[~2026-11-19 10:24 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-23 10:22 [PATCH 0/5] devtool: Support multiconfig workflows and fix kernel extraction Anusmita Dutta Mazumder
2026-10-23 10:22 ` [PATCH 1/5] devtool: Support multiconfig recipe workflows Anusmita Dutta Mazumder
2026-10-23 10:22 ` [PATCH 2/5] devtool: Check kernel configure result Anusmita Dutta Mazumder
2026-10-23 10:22 ` [PATCH 3/5] devtool: Isolate multiconfig workspace entries Anusmita Dutta Mazumder
2026-10-23 10:22 ` [PATCH 4/5] devtool: Record kernel baseline after revision validation Anusmita Dutta Mazumder
2026-10-23 10:22 ` [PATCH 5/5] oe-selftest: devtool: Add multiconfig workflow tests Anusmita Dutta Mazumder
2026-10-26  0:09 ` [OE-core] [PATCH 0/5] devtool: Support multiconfig workflows and fix kernel extraction adrian.freihofer
2026-10-28 15:10   ` Anusmita Dutta Mazumder
2026-11-19 10:24     ` Anusmita Dutta Mazumder [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=966833.1795083845075041074@lists.openembedded.org \
    --to=anusmita.duttamazumder@arm.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