From: "Kavinaya S" <kavinaya@qti.qualcomm.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH v4 1/1] fitimage: Add support for custom compatible string via optional parameter
Date: Wed, 08 Oct 2025 11:05:39 -0700 [thread overview]
Message-ID: <23671.1759946739005281989@lists.openembedded.org> (raw)
In-Reply-To: <gahunfldkpx3p453csdcoxnosrvbcnnzoeamsmxvzxxesvyls4@v4eicwchoz3p>
On Mon, Oct 6, 2025 at 04:04 AM, Dmitry Baryshkov wrote:
>
> Can't you seetle on one format? Whitespace-separated string should be
> fine, it's the format that is commonly accepted by other routines.
>
Sure, will settle to whitespace-separated format.
next prev parent reply other threads:[~2025-10-08 18:05 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-30 6:51 [PATCH v4 0/1] Add support for custom compatible string via optional parameter Kavinaya S
2025-09-30 6:51 ` [PATCH v4 1/1] fitimage: " Kavinaya S
2025-09-30 11:01 ` Alexander Kanavin
2025-10-05 22:36 ` Dmitry Baryshkov
2025-10-08 18:07 ` Kavinaya S
2025-10-05 22:34 ` Dmitry Baryshkov
2025-10-08 18:03 ` Kavinaya S
2025-10-08 18:05 ` Kavinaya S
2025-10-08 18:05 ` Kavinaya S [this message]
2025-10-08 18:06 ` Kavinaya S
2025-10-05 22:26 ` [PATCH v4 0/1] " Dmitry Baryshkov
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=23671.1759946739005281989@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