Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: "AshishKumar Mishra" <ashishkumar.mishra@bmwtechworks.in>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [meta-oe][PATCH v4 1/4] android-tools: remove android-tools 5.x from meta-oe/recipes-devtools
Date: Tue, 09 Jun 2026 03:36:48 -0700	[thread overview]
Message-ID: <20362.1781001408536239294@lists.openembedded.org> (raw)
In-Reply-To: <relbc3u3fwyfvt37xybbegkc2iezia7xelbyo4tjh6n77xt4i5@dvjvs2whwggq>

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

Hi Dmitry,

Sorry for the breakage, and thanks for catching it and helping with the partial revert to fix the regression.

This was an oversight on my end.

I had verified that the build compiled fine for an RPI4 target with core-image-minimal (qemuarm with GCC and CLANG) ,
but since that was only a compile-time check and I didn’t flash it on real hardware running a mainline kernel,
the missing ConfigFS scripts slipped through.

I want to avoid missing this kind of issue on future upgrades.
- Could you share the testing or sanity-checking workflow you usually follow for userspace/kernel integrations like this?
- Are there specific QEMU configs, runtime checks, or review habits you rely on to make sure upstream compatibility doesn’t break?

I’d like to adapt my own workflow so I can catch this kind of runtime regression earlier.

Thanks again for the guidance.
Ashish

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

  reply	other threads:[~2026-06-09 10:36 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-24  6:53 [meta-oe][PATCH v4 0/4] android-tools: migration and cleanup AshishKumar Mishra
2026-05-24  6:53 ` [meta-oe][PATCH v4 1/4] android-tools: remove android-tools 5.x from meta-oe/recipes-devtools AshishKumar Mishra
2026-06-09 10:05   ` Dmitry Baryshkov
2026-06-09 10:36     ` AshishKumar Mishra [this message]
2026-05-24  6:53 ` [meta-oe][PATCH v4 2/4] android-tools: move android-tools v29.x from dynamic-layers/selinux to meta-oe AshishKumar Mishra
2026-05-24  6:53 ` [meta-oe][PATCH v4 3/4] android-tools: removes selinux dependency from android-tools_29.0.6.r14.bb AshishKumar Mishra
2026-05-24  6:53 ` [meta-oe][PATCH v4 4/4] android-tools: fix deprecated header warning from clang AshishKumar Mishra
2026-05-28 10:47 ` [meta-oe][PATCH v4 0/4] android-tools: migration and cleanup AshishKumar Mishra
2026-05-29  8:51   ` [oe] " Khem Raj

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=20362.1781001408536239294@lists.openembedded.org \
    --to=ashishkumar.mishra@bmwtechworks.in \
    --cc=openembedded-devel@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