On Sun, Jan 9, 2022 at 5:32 PM Sean Anderson wrote:
> Do you want me to send a PR for this or can you pick it up directly?
This one has already been applied:
https://source.denx.de/u-boot/u-boot/-/commit/75f080df46f28f24a617652c8af028cc349f908b
Hi Tom,
On 1/5/22 3:57 PM, Tom Rini wrote:
I will defer to the clock maintainer who I see agrees with your patch.
I was just noting that we'd already shipped one release so a last minute
revert is not something I'm happy about either.
Do you want me to send a PR for this or can you pick it up
On Sat, Jan 01, 2022 at 07:51:39PM +0100, Marek Vasut wrote:
> This reverts commit 92f1e9a4b31c0bf0f4f61ab823a6a88657323646.
> The aforementioned patch causes massive breakage on all platforms which
> have 'assigned-clock' DT property in their DT which references any clock
> that are not supported
Hi,
On Wed, 5 Jan 2022 at 13:57, Tom Rini wrote:
>
> On Wed, Jan 05, 2022 at 08:56:50PM +0100, Marek Vasut wrote:
> > On 1/5/22 20:37, Tom Rini wrote:
> > > On Wed, Jan 05, 2022 at 08:35:19PM +0100, Marek Vasut wrote:
> > > > On 1/1/22 22:41, Sean Anderson wrote:
> > > > > Hi Marek,
> > > >
> > >
On Wed, Jan 05, 2022 at 08:56:50PM +0100, Marek Vasut wrote:
> On 1/5/22 20:37, Tom Rini wrote:
> > On Wed, Jan 05, 2022 at 08:35:19PM +0100, Marek Vasut wrote:
> > > On 1/1/22 22:41, Sean Anderson wrote:
> > > > Hi Marek,
> > >
> > > Hi,
> > >
> > > > Please CC clock maintainers for future patch
Hi Marek,
On Sat, Jan 1, 2022 at 3:51 PM Marek Vasut wrote:
>
> This reverts commit 92f1e9a4b31c0bf0f4f61ab823a6a88657323646.
> The aforementioned patch causes massive breakage on all platforms which
> have 'assigned-clock' DT property in their DT which references any clock
> that are not support
On 1/5/22 2:37 PM, Tom Rini wrote:
On Wed, Jan 05, 2022 at 08:35:19PM +0100, Marek Vasut wrote:
On 1/1/22 22:41, Sean Anderson wrote:
Hi Marek,
Hi,
Please CC clock maintainers for future patches.
btw. I'm surprised the commit 92f1e9a4b31c0bf0f4f61ab823a6a88657323646 has
zero reviews/acks
On 1/5/22 20:37, Tom Rini wrote:
On Wed, Jan 05, 2022 at 08:35:19PM +0100, Marek Vasut wrote:
On 1/1/22 22:41, Sean Anderson wrote:
Hi Marek,
Hi,
Please CC clock maintainers for future patches.
btw. I'm surprised the commit 92f1e9a4b31c0bf0f4f61ab823a6a88657323646 has
zero reviews/acks fr
On Wed, Jan 05, 2022 at 08:35:19PM +0100, Marek Vasut wrote:
> On 1/1/22 22:41, Sean Anderson wrote:
> > Hi Marek,
>
> Hi,
>
> > Please CC clock maintainers for future patches.
>
> btw. I'm surprised the commit 92f1e9a4b31c0bf0f4f61ab823a6a88657323646 has
> zero reviews/acks from clock maintaine
On 1/1/22 22:41, Sean Anderson wrote:
Hi Marek,
Hi,
Please CC clock maintainers for future patches.
btw. I'm surprised the commit 92f1e9a4b31c0bf0f4f61ab823a6a88657323646
has zero reviews/acks from clock maintainers.
On 1/1/22 1:51 PM, Marek Vasut wrote:
This reverts commit 92f1e9a4b31
Hi Marek,
Please CC clock maintainers for future patches.
On 1/1/22 1:51 PM, Marek Vasut wrote:
This reverts commit 92f1e9a4b31c0bf0f4f61ab823a6a88657323646.
The aforementioned patch causes massive breakage on all platforms which
have 'assigned-clock' DT property in their DT which references an
This reverts commit 92f1e9a4b31c0bf0f4f61ab823a6a88657323646.
The aforementioned patch causes massive breakage on all platforms which
have 'assigned-clock' DT property in their DT which references any clock
that are not supported by the platform clock driver. That can easily
happen either in SPL, o
12 matches
Mail list logo
