From: Mattijs Korpershoek <mkorpershoek@baylibre.com>
To: Tom Rini <trini@konsulko.com>
Cc: Lukasz Majewski <lukma@denx.de>, u-boot@lists.denx.de
Subject: [GIT PULL] Please pull u-boot-dfu-20231103
Date: Fri, 03 Nov 2023 14:34:35 +0100 [thread overview]
Message-ID: <87v8ajm044.fsf@baylibre.com> (raw)
Hi Tom,
Here is my first pull request of u-boot-dfu which includes:
- Fix CRC chunk size in fastboot
- Make size optional for dfu on mmc
The CI job is at https://source.denx.de/u-boot/custodians/u-boot-dfu/-/pipelines/18433
Thanks,
Mattijs
The following changes since commit cbba1b7766bd93d74e28202c46e69095ac13760b:
Merge branch '2023-10-30-assorted-general-updates' (2023-10-30 16:01:54 -0400)
are available in the Git repository at:
https://source.denx.de/u-boot/custodians/u-boot-dfu.git tags/u-boot-dfu-20231103
for you to fetch changes up to 60d904a494c6e89c323bc13fa9348869e07e86d3:
dfu: mmc: Add support for exposing whole mmc device (2023-10-31 14:53:05 +0100)
----------------------------------------------------------------
u-boot-dfu-20231103
- Fix CRC chunk size in fastboot
- Make size optional for dfu on mmc
----------------------------------------------------------------
Marek Vasut (1):
dfu: mmc: Add support for exposing whole mmc device
Wojciech Nizinski (1):
fastboot: fix CRC32 chunk size checking
doc/usage/dfu.rst | 5 +++++
drivers/dfu/dfu_mmc.c | 10 ++++++++++
lib/image-sparse.c | 4 ++--
3 files changed, 17 insertions(+), 2 deletions(-)
next reply other threads:[~2023-11-03 13:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-03 13:34 Mattijs Korpershoek [this message]
2023-11-04 13:57 ` [GIT PULL] Please pull u-boot-dfu-20231103 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=87v8ajm044.fsf@baylibre.com \
--to=mkorpershoek@baylibre.com \
--cc=lukma@denx.de \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.