u-boot.lists.denx.de archive mirror
 help / color / mirror / Atom feed
From: Matthias Brugger <mbrugger@suse.com>
To: Tom Rini <trini@konsulko.com>
Cc: "u-boot@lists.denx.de" <u-boot@lists.denx.de>,
	Peter Robinson <pbrobinson@gmail.com>,
	Mike Karels <karels@FreeBSD.org>
Subject: [GIT PULL] rpi: updates for v2022.01
Date: Wed, 15 Dec 2021 17:27:39 +0100	[thread overview]
Message-ID: <d6f520c6-ff67-41a5-68a9-12098c99c2ae@suse.com> (raw)

Hi Tom,

Here come a small set of patches for v2022.01 for the RaspberryPi.

You can find the passing tests here:
https://source.denx.de/u-boot/custodians/u-boot-raspberrypi/-/pipelines/10047

It's the same commit ID as the tag, although it's not the same test-run.

Regards,
Matthias

---

The following changes since commit ade37460a944aed36ae6ee634c4d4a9a22690461:



   Prepare v2022.01-rc3 (2021-11-29 11:16:03 -0500)



are available in the Git repository at:



   https://source.denx.de/u-boot/custodians/u-boot-raspberrypi.git 
tags/rpi-next-2022.01



for you to fetch changes up to 874e544e89a7f9f42796b23f8d43c56e203b6e69:



   Fix MMC numbering issue for Raspberry Pi 3 (2021-11-30 16:07:40 +0100)



----------------------------------------------------------------

- enable RPi Zero 2 W

- fix MMC numbering issue

- Update link to documentation



----------------------------------------------------------------

Mike Karels (1):

       Fix MMC numbering issue for Raspberry Pi 3



Peter Robinson (2):

       rpi: Update the Raspberry Pi doucmentation URL

       rpi: Add identifier for the new RPi Zero 2 W



  board/raspberrypi/rpi/rpi.c | 7 ++++++-

  include/configs/rpi.h       | 3 ++-

  2 files changed, 8 insertions(+), 2 deletions(-)


             reply	other threads:[~2021-12-15 16:27 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-15 16:27 Matthias Brugger [this message]
2021-12-15 23:22 ` [GIT PULL] rpi: updates for v2022.01 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=d6f520c6-ff67-41a5-68a9-12098c99c2ae@suse.com \
    --to=mbrugger@suse.com \
    --cc=karels@FreeBSD.org \
    --cc=pbrobinson@gmail.com \
    --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;
as well as URLs for NNTP newsgroup(s).