From: Mattijs Korpershoek <mkorpershoek@kernel.org>
To: Tom Rini <trini@konsulko.com>, u-boot@lists.denx.de
Cc: Lukasz Majewski <lukma@denx.de>,
Andrew Goodbody <andrew.goodbody@linaro.org>
Subject: [GIT PULL] Please pull u-boot-dfu-next-20250703 into next
Date: Thu, 03 Jul 2025 16:11:34 +0200 [thread overview]
Message-ID: <87pleh4b55.fsf@kernel.org> (raw)
Hi Tom,
Please find the following fixes/developments for next:
Android:
- Fix uninitialized vhdr pointer in image-android.c
- Fix uninitialized vhdr pointer in abootimg cmd
DFU:
- Update maintainers file to include spl/spl_dfu
CI Job:
- https://source.denx.de/u-boot/custodians/u-boot-dfu/-/pipelines/26938
Thanks,
Mattijs
The following changes since commit cbb5672790d400e9ec6e9fceaf89ece2660c0117:
Merge patch series "binman: properly error out if path provided to key-name-hint in signature nodes" (2025-07-01 10:52:04 -0600)
are available in the Git repository at:
https://source.denx.de/u-boot/custodians/u-boot-dfu.git tags/u-boot-dfu-next-20250703
for you to fetch changes up to 4b489f517366595cd3f003d4175e721bd927a18b:
boot: android: Prevent use of unintialised variable (2025-07-02 12:10:25 +0200)
----------------------------------------------------------------
u-boot-dfu-next-20250703
Android:
- Fix uninitialized vhdr pointer in image-android.c
- Fix uninitialized vhdr pointer in abootimg cmd
DFU:
- Update maintainers file to include spl/spl_dfu
----------------------------------------------------------------
Andrew Goodbody (2):
cmd: abootimg: Prevent use of unintialised variable
boot: android: Prevent use of unintialised variable
Mattijs Korpershoek (1):
MAINTAINERS: Add common/spl/spl_dfu to DFU entry
MAINTAINERS | 1 +
boot/image-android.c | 2 +-
cmd/abootimg.c | 2 +-
3 files changed, 3 insertions(+), 2 deletions(-)
next reply other threads:[~2025-07-03 14:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-03 14:11 Mattijs Korpershoek [this message]
2025-07-03 16:29 ` [GIT PULL] Please pull u-boot-dfu-next-20250703 into next 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=87pleh4b55.fsf@kernel.org \
--to=mkorpershoek@kernel.org \
--cc=andrew.goodbody@linaro.org \
--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.