From: Tony Lindgren <tony@atomide.com>
To: Paul Barker <paul.barker@sancloud.com>
Cc: "Robert Nelson" <robertcnelson@gmail.com>,
"Benoît Cousson" <bcousson@baylibre.com>,
linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
devicetree@vger.kernel.org
Subject: Re: [PATCH v2 0/4] Add support for the SanCloud BBE Lite
Date: Thu, 5 Aug 2021 11:48:08 +0300 [thread overview]
Message-ID: <YQulyGLNNkyYcBSY@atomide.com> (raw)
In-Reply-To: <20210804115221.5650e440.paul.barker@sancloud.com>
[-- Attachment #1.1: Type: text/plain, Size: 997 bytes --]
* Paul Barker <paul.barker@sancloud.com> [210804 10:52]:
> On Tue, 27 Jul 2021 11:55:21 +0300
> Tony Lindgren <tony@atomide.com> wrote:
>
> > * Paul Barker <paul.barker@sancloud.com> [210720 11:40]:
> > > The Lite variant of the SanCloud BeagleBone Enhanced (BBE) removes the
> > > HDMI encoder, barometer and accelerometer chips and adds a Micron
> > > Authenta SPI flash chip.
> >
> > Thanks applying all for v5.15 merge window.
>
> I tested the for-next branch of linux-omap to confirm that things
> worked with these patches applied. There was a NULL pointer
> dereference in ptp_clock_register() during boot. The fix appears to be
> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=55eac20617ca84129273ab248f4d7bfe456967de
> which went into 5.14-rc2.
Yeah so it seems, too bad it was not there for -rc1 already.
> Merging for-next with 5.14-rc4 resulted in things working as expected.
OK thanks for checking.
Regards,
Tony
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
[-- Attachment #2: Type: text/plain, Size: 176 bytes --]
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2021-08-05 8:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-20 8:39 [PATCH v2 0/4] Add support for the SanCloud BBE Lite Paul Barker
2021-07-20 8:39 ` [PATCH v2 1/4] ARM: dts: am335x-boneblack: Extract HDMI config Paul Barker
2021-07-20 8:39 ` [PATCH v2 2/4] ARM: dts: am335x-sancloud-bbe: Extract common code Paul Barker
2021-07-20 8:39 ` [PATCH v2 3/4] ARM: dts: am335x-sancloud-bbe-lite: New devicetree Paul Barker
2021-07-20 8:39 ` [PATCH v2 4/4] MAINTAINERS: Adopt SanCloud dts files as supported Paul Barker
2021-07-27 8:55 ` [PATCH v2 0/4] Add support for the SanCloud BBE Lite Tony Lindgren
2021-08-04 10:52 ` Paul Barker
2021-08-05 8:48 ` Tony Lindgren [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=YQulyGLNNkyYcBSY@atomide.com \
--to=tony@atomide.com \
--cc=bcousson@baylibre.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=paul.barker@sancloud.com \
--cc=robertcnelson@gmail.com \
/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).