From: Tom Rini <email@example.com>
To: Vincent Fazio <firstname.lastname@example.org>
Cc: Peter Robinson <email@example.com>,
Matthias Brugger <firstname.lastname@example.org>,
Marek Szyprowski <email@example.com>,
"Ivan T. Ivanov" <firstname.lastname@example.org>
Subject: Re: [GIT PULL] rpi: updates for v2021.10
Date: Wed, 15 Sep 2021 13:44:45 -0400 [thread overview]
Message-ID: <20210915174445.GX12964@bill-the-cat> (raw)
[-- Attachment #1: Type: text/plain, Size: 1747 bytes --]
On Wed, Sep 15, 2021 at 12:40:29PM -0500, Vincent Fazio wrote:
> On 9/15/21 11:32 AM, Peter Robinson wrote:
> > On Wed, Sep 15, 2021 at 4:40 PM Matthias Brugger <email@example.com> wrote:
> > > Hi Tom,
> > >
> > > I know, quite a bit late but here come the updates for RPi for v2021.10.
> > > Actually most of the patches are fixes.
> > >
> > > Ivan's patch fixes a kernel warning when booting RPi2, as the firmware already
> > > provides a frambebuffer node.
> > >
> > > Marek's patch fixes random crashes on 32 bit RPi4 with newer firmware.
> > >
> > > My SMBIOS patchesfixes an issue that show up with
> > > e4f8e543f1 ("smbios: Drop the unused Kconfig options").
> > > Basically the SMBIOS table broke and wasn't readable anymore.
> > >
> > > I think we can argue if the last one is a real fix. In case you just want to
> > > take the first two so late in the cycle, let me know and I can provide you with
> > > a separate pull request.
> > It would also be good to get these , although it doesn't seem like
> > they were also posted to the list. It fixes a regression with U-Boot
> > and recent RPi firmwares  so will likely come up sooner rather than
> > later post release.
> > Peter
> I did send these to the u-boot list but received an "awaiting moderator
> approval" response.
> Is there a different list i should have submitted this to, just for future
> >  https://patchwork.ozlabs.org/project/uboot/list/?series=262375
This is the correct list. That it's in patchwork means it went to the
list, even. Moderator approval happens a few times a day (US/Eastern)
or when I see a number of obviously not spam requests go by, JFYI.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 659 bytes --]
next prev parent reply other threads:[~2021-09-15 17:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-15 15:39 [GIT PULL] rpi: updates for v2021.10 Matthias Brugger
2021-09-15 16:32 ` Peter Robinson
2021-09-15 17:40 ` Vincent Fazio
2021-09-15 17:44 ` Tom Rini [this message]
2021-09-15 21:05 ` Tom Rini
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:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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.