From: "Neil Armstrong" <narmstrong@baylibre.com>
To: trini@konsulko.com
Cc: u-boot-amlogic@groups.io, u-boot@lists.denx.de
Subject: [GIT PULL] Please pull u-boot-amlogic-20220809
Date: Tue, 9 Aug 2022 10:21:42 +0200 [thread overview]
Message-ID: <7635ad28-344c-4a83-03aa-c23c3fd866d0@baylibre.com> (raw)
Hi Tom,
Here's changes for next release:
- fixup error on efuse commands return
- add documentation on boot flow
The CI job is at https://source.denx.de/u-boot/custodians/u-boot-amlogic/pipelines/13087
Thanks,
Neil
The following changes since commit 2d2c61ff0460740d9ec5a44dbef9255a8c690696:
Merge tag 'efi-2022-07-rc7' of https://source.denx.de/u-boot/custodians/u-boot-efi (2022-07-06 09:17:08 -0400)
are available in the Git repository at:
https://source.denx.de/u-boot/custodians/u-boot-amlogic.git tags/u-boot-amlogic-20220809
for you to fetch changes up to 3145e0d0ff0837647351f2ca261b4cde779f83e0:
ARM: meson: fixup error on efuse commands return (2022-08-08 09:56:38 +0200)
----------------------------------------------------------------
- fixup error on efuse commands return
- add documentation on boot flow
----------------------------------------------------------------
Jerome Brunet (1):
ARM: meson: fixup error on efuse commands return
Neil Armstrong (1):
doc: board: amlogic: add documentation on boot flow
arch/arm/mach-meson/sm.c | 9 +--
doc/board/amlogic/boot-flow.rst | 134 ++++++++++++++++++++++++++++++++++++++++
doc/board/amlogic/index.rst | 1 +
3 files changed, 138 insertions(+), 6 deletions(-)
create mode 100644 doc/board/amlogic/boot-flow.rst
next reply other threads:[~2022-08-09 8:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-09 8:21 Neil Armstrong [this message]
2022-08-09 16:33 ` [GIT PULL] Please pull u-boot-amlogic-20220809 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=7635ad28-344c-4a83-03aa-c23c3fd866d0@baylibre.com \
--to=narmstrong@baylibre.com \
--cc=trini@konsulko.com \
--cc=u-boot-amlogic@groups.io \
--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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).