From: Mattijs Korpershoek <mkorpershoek@baylibre.com>
To: Jaehoon Chung <jh80.chung@samsung.com>
Cc: lukma@denx.de, u-boot@lists.denx.de
Subject: Re: [PATCH] dfu: add CONFIG_DFU_NAME_MAX_SIZE configuration
Date: Thu, 02 Nov 2023 10:15:14 +0100 [thread overview]
Message-ID: <87h6m4zfbx.fsf@baylibre.com> (raw)
In-Reply-To: <169876380794.37728.2863914527348419844.b4-ty@baylibre.com>
Hi Jaehoon,
On mar., oct. 31, 2023 at 15:50, Mattijs Korpershoek <mkorpershoek@baylibre.com> wrote:
> Hi,
>
> On Mon, 20 Jun 2022 20:13:54 +0900, Jaehoon Chung wrote:
>> Add CONFIG_DFU_NAME_MAX_SIZE to change the proper size.
>> If name is longer than default size, it can do wrong behavior during updating
>> image. So it need to change the proper maximum size.
>>
>> This patch is proviced the solution to change value with configuration.
>>
>>
>> [...]
>
> Thanks, Applied to https://source.denx.de/u-boot/custodians/u-boot-dfu (u-boot-dfu-next)
>
> [1/1] dfu: add CONFIG_DFU_NAME_MAX_SIZE configuration
> https://source.denx.de/u-boot/custodians/u-boot-dfu/-/commit/de9b2e10f10996050a10998a0836abe2f9e425e3
This patch breaks CI for both arm32 and arm64 platforms:
* https://source.denx.de/u-boot/custodians/u-boot-dfu/-/jobs/725163
* https://source.denx.de/u-boot/custodians/u-boot-dfu/-/jobs/725164
It breaks because multiple boards which include dfu.h without having
CONFIG_DFU being set.
Tom attempted to fix this with:
https://patchwork.ozlabs.org/project/uboot/list/?series=369275
But that had some different issues, see:
https://libera.irclog.whitequark.org/u-boot/2023-10-31#35154532;
I've fixed it up with the following diff:
diff --git a/include/dfu.h b/include/dfu.h
index 4573f753c565..2c3ffa3f9297 100644
--- a/include/dfu.h
+++ b/include/dfu.h
@@ -99,7 +99,12 @@ struct virt_internal_data {
int dev_num;
};
+
+#if defined(CONFIG_DFU_NAME_MAX_SIZE)
#define DFU_NAME_SIZE CONFIG_DFU_NAME_MAX_SIZE
+#else
+#define DFU_NAME_SIZE 32
+#endif
#ifndef DFU_DEFAULT_POLL_TIMEOUT
#define DFU_DEFAULT_POLL_TIMEOUT 0
#endif
If you have a better idea to fix this, can you please let me know?
Otherwise, I will squash this to keep CI green.
Thank you
>
> --
> Mattijs
next prev parent reply other threads:[~2023-11-02 9:15 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20220620111357epcas1p103474818319b5dc45260e043b4ffe3cc@epcas1p1.samsung.com>
2022-06-20 11:13 ` [PATCH] dfu: add CONFIG_DFU_NAME_MAX_SIZE configuration Jaehoon Chung
2022-06-20 11:23 ` Lukasz Majewski
2023-10-31 14:47 ` Mattijs Korpershoek
2023-10-31 14:50 ` Mattijs Korpershoek
2023-11-02 9:15 ` Mattijs Korpershoek [this message]
2023-11-03 1:07 ` Jaehoon Chung
2023-11-03 5:49 ` Jaehoon Chung
2023-11-07 9:08 ` Mattijs Korpershoek
2023-11-03 9:43 ` Mattijs Korpershoek
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=87h6m4zfbx.fsf@baylibre.com \
--to=mkorpershoek@baylibre.com \
--cc=jh80.chung@samsung.com \
--cc=lukma@denx.de \
--cc=u-boot@lists.denx.de \
/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