From: Matthias Brugger <matthias.bgg@gmail.com>
To: u-boot@lists.denx.de
Subject: [GIT PULL] rpi: second round for v2020.10
Date: Thu, 10 Sep 2020 09:45:42 +0200 [thread overview]
Message-ID: <de888eac-a041-8a7e-73d0-0747de0b3fcd@gmail.com> (raw)
In-Reply-To: <20200909212011.1719ff27@ezekiel.suse.cz>
On 09/09/2020 21:20, Petr Tesarik wrote:
> On Wed, 9 Sep 2020 10:13:50 +0200
> Matthias Brugger <matthias.bgg@gmail.com> 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.
>
> What do you mean by "didn't come through"? I can see it in the mailing
> list archive:
>
> http://u-boot.10912.n7.nabble.com/PATCH-bcmgenet-fix-DMA-buffer-management-td419536.html#a424854
>
> Did I send my answer to the wrong thread?
Ups, it seems I rely too much on my inbox instead of the filtered U-Boot list.
In any case I exepcted the Tested-by for the two patches you mentioned in the
thread.
Anyway it's no big deal.
Regards,
Matthias
>
> Petr T
>
>> 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)
>>
>> ----------------------------------------------------------------
>> - fixes for bcmgenet
>> - enable USB keyboard for RPi4 32 bit
>>
>> ----------------------------------------------------------------
>> Jason Wessel (2):
>> bcmgenet: fix DMA buffer management
>> bcmgenet: Add support for rgmii-rxid
>>
>> Matthias Brugger (1):
>> config: Enable USB Keyboard suuport on RPi4 32 bit
>>
>> configs/rpi_4_32b_defconfig | 1 +
>> drivers/net/bcmgenet.c | 20 +++++++++++---------
>> 2 files changed, 12 insertions(+), 9 deletions(-)
>>
>
prev parent reply other threads:[~2020-09-10 7:45 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
2020-09-09 19:20 ` Petr Tesarik
2020-09-10 7:45 ` Matthias Brugger [this message]
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=de888eac-a041-8a7e-73d0-0747de0b3fcd@gmail.com \
--to=matthias.bgg@gmail.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