From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de
Subject: [GIT PULL] rpi: second round for v2020.10
Date: Wed, 9 Sep 2020 10:20:23 -0400 [thread overview]
Message-ID: <20200909142023.GQ7259@bill-the-cat> (raw)
In-Reply-To: <ed8dbdb4-8cc9-6e0c-d90b-4f91647212b3@gmail.com>
On Wed, Sep 09, 2020 at 10:13:50AM +0200, Matthias Brugger wrote:
> Hi Tom,
>
> Please have a look at the second round of patches for the RPi. Two patches
> fixes the network driver of the RPi4 which didn't work reliable. Another
> patch enables USB keyboard for 32 bit RPi4.
>
> Petr tested the network patches, but his mail with the Tested-by tag didn't
> come through. I added it anyway.
>
> As always you can find the CI outcome here:
> https://travis-ci.org/github/mbgg/u-boot/builds/725262009
> https://gitlab.denx.de/u-boot/custodians/u-boot-raspberrypi/-/pipelines/4622
>
> I ran the CI against the rpi-next branch and not the tag, but you can verify
> that this is basically the same commit id.
>
> Thanks for having a look!
> Regards,
> Matthias
>
> --
>
> The following changes since commit 96d66a9b8ce11aae9f8bef5244b83b4740b37644:
>
> Prepare v2020.10-rc4 (2020-09-07 14:17:33 -0400)
>
> are available in the Git repository at:
>
> https://gitlab.denx.de/u-boot/custodians/u-boot-raspberrypi.git/
> tags/rpi-next-2020.10.2
>
> for you to fetch changes up to 40877a1a949edf7066b3e4ed16101153624bb314:
>
> config: Enable USB Keyboard suuport on RPi4 32 bit (2020-09-08 16:45:01 +0200)
>
Applied to u-boot/master, thanks!
--
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 659 bytes
Desc: not available
URL: <https://lists.denx.de/pipermail/u-boot/attachments/20200909/bc61e4b7/attachment.sig>
next prev parent reply other threads:[~2020-09-09 14:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-09 8:13 [GIT PULL] rpi: second round for v2020.10 Matthias Brugger
2020-09-09 14:20 ` Tom Rini [this message]
2020-09-09 19:20 ` Petr Tesarik
2020-09-10 7:45 ` Matthias Brugger
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=20200909142023.GQ7259@bill-the-cat \
--to=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