On Mon, Feb 10, 2025 at 03:57:42PM +, J. Neuschäfer wrote:
> On Mon, Feb 10, 2025 at 12:59:35PM +, Mark Brown wrote:
> > Please don't do this, it just makes it harder to merge things since it
> > makes it look like there's cross tree merges needed when that's not the
> > case, complicating
On Mon, Feb 10, 2025 at 12:59:35PM +, Mark Brown wrote:
> On Sat, Feb 08, 2025 at 02:20:47AM +, J. Neuschäfer wrote:
> > On Fri, Feb 07, 2025 at 09:38:05PM +, Mark Brown wrote:
>
> > > What's the story with dependencies here - why is all this stuff in one
> > > series?
>
> > The patch
On Sat, Feb 08, 2025 at 02:20:47AM +, J. Neuschäfer wrote:
> On Fri, Feb 07, 2025 at 09:38:05PM +, Mark Brown wrote:
> > What's the story with dependencies here - why is all this stuff in one
> > series?
> The patches are independent of each other, except for the four elbc/nand
> patches.
On Fri, Feb 07, 2025 at 09:38:05PM +, Mark Brown wrote:
> On Fri, Feb 07, 2025 at 10:30:17PM +0100, J. Neuschäfer via B4 Relay wrote:
>
> > This is a spin-off of the series titled
> > "powerpc: MPC83xx cleanup and LANCOM NWAPP2 board".
>
> > During the development of that series, it became cl
This is a spin-off of the series titled
"powerpc: MPC83xx cleanup and LANCOM NWAPP2 board".
During the development of that series, it became clear that many
devicetree bindings for Freescale MPC8xxx platforms are still in the old
plain-text format, or don't exist at all, and in any case don't ment
On Fri, Feb 07, 2025 at 10:30:17PM +0100, J. Neuschäfer via B4 Relay wrote:
> This is a spin-off of the series titled
> "powerpc: MPC83xx cleanup and LANCOM NWAPP2 board".
> During the development of that series, it became clear that many
> devicetree bindings for Freescale MPC8xxx platforms are
