From: kavinaya@qti.qualcomm.com
To: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 1/2] kernel-fitimage: add support for custom ITS file override
Date: Mon, 29 Sep 2025 07:26:45 -0700 [thread overview]
Message-ID: <18494.1759156005270288938@lists.openembedded.org> (raw)
In-Reply-To: <CANNYZj9RXcePZWt4VfMqxdyARDLyoEkmdhnmF0vueTskcJgE5Q@mail.gmail.com>
On Fri, Sep 26, 2025 at 01:01 PM, Alexander Kanavin wrote:
>
> Using custom files with unclear, unspecified ways to produce them also
> fragments the ecosystem and inserts vendor magic and
> non-reproducibility into the build process. That is a negative impact
> on the project, and goes against its principles.
>
> Fixing the ITS generator is still the preferred solution, even if it
> requires more work on your part, possibly including writing tests.
>
Hi Alexander,
Thanks for the feedback. I’ll address these concerns by extending the ITS generator instead of using custom ITS files, ensuring the
solution remains reproducible and aligned with project principles. I’ll also add tests as needed.
Thanks,
Kavinaya
next prev parent reply other threads:[~2025-09-29 14:26 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250919073335.2069114-1-kavinaya@qti.qualcomm.com>
2025-09-19 7:33 ` [PATCH 1/2] kernel-fitimage: add support for custom ITS file override Kavinaya S
2025-09-21 11:40 ` [OE-core] " Freihofer, Adrian
2025-09-22 8:41 ` kavinaya
2025-09-22 9:58 ` [OE-core] " Alexander Kanavin
[not found] ` <1867495AF42A64B8.23261@lists.openembedded.org>
2025-09-22 20:58 ` Freihofer, Adrian
2025-09-24 8:30 ` kavinaya
2025-09-24 9:46 ` kavinaya
2025-09-26 3:42 ` kavinaya
2025-09-26 7:31 ` [OE-core] " Alexander Kanavin
2025-09-29 14:26 ` kavinaya [this message]
2025-09-19 7:33 ` [PATCH 2/2] image-fitimage.conf: introduce CUSTOM_ITS_FILE variable Kavinaya S
2025-09-22 9:44 ` [OE-core] " Alexander Kanavin
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=18494.1759156005270288938@lists.openembedded.org \
--to=kavinaya@qti.qualcomm.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