From: Mattijs Korpershoek <mkorpershoek@baylibre.com>
To: Jon Humphreys <j-humphreys@ti.com>,
Ilias Apalodimas <ilias.apalodimas@linaro.org>
Cc: Sughosh Ganu <sughosh.ganu@linaro.org>,
Rasmus Villemoes <rasmus.villemoes@prevas.dk>,
Caleb Connolly <caleb.connolly@linaro.org>,
Tom Rini <trini@konsulko.com>, Lukasz Majewski <lukma@denx.de>,
s-vadapalli@ti.com, Heinrich Schuchardt <xypron.glpk@gmx.de>,
u-boot@lists.denx.de
Subject: Re: [PATCH] dfu: Prevent set_dfu_alt_info() from overwriting a previous value
Date: Tue, 04 Feb 2025 15:31:20 +0100 [thread overview]
Message-ID: <87r04dkchz.fsf@baylibre.com> (raw)
In-Reply-To: <864j1apv38.fsf@udb0321960.dhcp.ti.com>
On lun., févr. 03, 2025 at 15:38, Jon Humphreys <j-humphreys@ti.com> wrote:
> Ilias Apalodimas <ilias.apalodimas@linaro.org> writes:
[...]
>>
>
> I went with option 1 above. I started working on option 2 however the
> changes are quite invasive, touching all of the DFU interfaces, and I do not
> have the understanding of the different DFU use cases nor access to the
> different hardware using those use cases to test. I also think that this
> change should be part of a broader DFU cleanup to use only the latest
> dfu_alt_info string format allowing multiple devices, so that we no longer
> need to pass around the interface and devstr parameters.
>
> Please take a look at the patch series titled "EFI Capsule update
> explicitly sets dfu_alt_info" that I will post shortly.
For future reference, this is the mentioned series:
http://lore.kernel.org/r/20250203215351.2840144-1-j-humphreys@ti.com/
>
> thanks
> Jon
>
[...]
prev parent reply other threads:[~2025-02-04 14:31 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-17 20:48 [PATCH] dfu: Prevent set_dfu_alt_info() from overwriting a previous value Jonathan Humphreys
2024-12-18 4:54 ` Siddharth Vadapalli
2024-12-18 12:28 ` Mattijs Korpershoek
2024-12-18 23:09 ` Jon Humphreys
2025-01-16 8:37 ` Mattijs Korpershoek
2025-01-16 9:35 ` Ilias Apalodimas
2025-01-16 9:39 ` Sughosh Ganu
2025-01-16 22:02 ` Jon Humphreys
2025-01-17 10:47 ` Ilias Apalodimas
2025-02-03 21:38 ` Jon Humphreys
2025-02-04 12:57 ` Ilias Apalodimas
2025-02-04 14:31 ` Mattijs Korpershoek [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=87r04dkchz.fsf@baylibre.com \
--to=mkorpershoek@baylibre.com \
--cc=caleb.connolly@linaro.org \
--cc=ilias.apalodimas@linaro.org \
--cc=j-humphreys@ti.com \
--cc=lukma@denx.de \
--cc=rasmus.villemoes@prevas.dk \
--cc=s-vadapalli@ti.com \
--cc=sughosh.ganu@linaro.org \
--cc=trini@konsulko.com \
--cc=u-boot@lists.denx.de \
--cc=xypron.glpk@gmx.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