From: Masami Hiramatsu <masami.hiramatsu@linaro.org>
To: Tom Rini <trini@konsulko.com>, Lukasz Majewski <lukma@denx.de>
Cc: u-boot@lists.denx.de, ilias.apalodimas@linaro.org,
sughosh.ganu@linaro.org, jaswinder.singh@linaro.org
Subject: [PATCH v2 0/5] DFU: Update dfu_alt_info parser etc.
Date: Mon, 31 Jan 2022 11:52:11 +0900 [thread overview]
Message-ID: <164359753172.280839.8310577813724924540.stgit@localhost> (raw)
Hi,
Here is the 2nd version of improving DFU subsystem series.
This improves dfu_alt_info parser and fixing documents etc.
In this version I fixed a build error of cmd/dfu.c so that
it can be build without DFU_OVER_USB and DFU_OVER_TFTP
(in this case, the platform will use the DFU only for EFI
capsule update.)
When I was debuging my patch for updating dfu_alt_info on the
DeveloperBox platform, I found that dfu_alt_info parser didn't
accept redundant spaces and tabs. Also the dfu.rst description
seems wrong. Moreover, there is no way to check whether the
parser parses the dfu_alt_info correctly.
These patches fixes such issues. [1/5] is just for avoiding
buffer overrun, [2/5] and [3/5] improves dfu_alt_info parser
to accept redundant spaces and tabs, and check the number of
arguments strictly so that the parser (and user) can notice
any unexpected parameters. [4/5] fixes the documents (there
seems some wrong description maybe coming from copy&paste).
[5/5] allows user to run 'dfu list' even if the platform
doesn't support DFU_OVER_USB nor DFU_OVER_TFTP.
Thank you,
---
Masami Hiramatsu (5):
DFU: Do not copy the entity name over the buffer size
DFU: Accept redundant spaces and tabs in dfu_alt_info
DFU: Check the number of arguments and argument string strictly
doc: usage: DFU: Fix dfu_alt_info document
cmd/dfu: Enable 'dfu list' command without DFU_OVER_USB
cmd/dfu.c | 8 +++----
doc/usage/dfu.rst | 57 ++++++++++++++++++++++++++++++++++--------------
drivers/dfu/dfu.c | 37 ++++++++++++++++++++++++-------
drivers/dfu/dfu_mmc.c | 55 +++++++++++++++++++++++++++-------------------
drivers/dfu/dfu_mtd.c | 34 +++++++++++++++++++----------
drivers/dfu/dfu_nand.c | 34 ++++++++++++++++++-----------
drivers/dfu/dfu_ram.c | 24 ++++++++++----------
drivers/dfu/dfu_sf.c | 34 ++++++++++++++++++-----------
drivers/dfu/dfu_virt.c | 5 +++-
include/dfu.h | 33 ++++++++++++++++++----------
10 files changed, 205 insertions(+), 116 deletions(-)
--
Masami Hiramatsu <masami.hiramatsu@linaro.org>
next reply other threads:[~2022-01-31 2:52 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-31 2:52 Masami Hiramatsu [this message]
2022-01-31 2:52 ` [PATCH v2 1/5] DFU: Do not copy the entity name over the buffer size Masami Hiramatsu
2022-02-11 17:06 ` Tom Rini
2022-01-31 2:52 ` [PATCH v2 2/5] DFU: Accept redundant spaces and tabs in dfu_alt_info Masami Hiramatsu
2022-02-11 17:06 ` Tom Rini
2022-01-31 2:52 ` [PATCH v2 3/5] DFU: Check the number of arguments and argument string strictly Masami Hiramatsu
2022-02-11 17:06 ` Tom Rini
2022-08-09 14:11 ` Michal Simek
2022-08-10 0:19 ` AKASHI Takahiro
2022-01-31 2:52 ` [PATCH v2 4/5] doc: usage: DFU: Fix dfu_alt_info document Masami Hiramatsu
2022-02-11 17:06 ` Tom Rini
2022-01-31 2:52 ` [PATCH v2 5/5] cmd/dfu: Enable 'dfu list' command without DFU_OVER_USB Masami Hiramatsu
2022-02-11 17:06 ` Tom Rini
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=164359753172.280839.8310577813724924540.stgit@localhost \
--to=masami.hiramatsu@linaro.org \
--cc=ilias.apalodimas@linaro.org \
--cc=jaswinder.singh@linaro.org \
--cc=lukma@denx.de \
--cc=sughosh.ganu@linaro.org \
--cc=trini@konsulko.com \
--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