linux-kernel - Re: [PATCH] ARM: dts: aspeed: yosemite4: adjust secondary flash name

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <a180245323d06ce09697abb1ee9e83cc66e73db1.camel@codeconstruct.com.au>
Date: Wed, 08 Jan 2025 11:00:35 +1030
From: Andrew Jeffery <andrew@...econstruct.com.au>
To: Patrick Williams <patrick@...cx.xyz>
Cc: devicetree@...r.kernel.org, linux-arm-kernel@...ts.infradead.org, 
	linux-aspeed@...ts.ozlabs.org, linux-kernel@...r.kernel.org, Rob Herring
	 <robh@...nel.org>, Krzysztof Kozlowski <krzk+dt@...nel.org>, Conor Dooley
	 <conor+dt@...nel.org>, Joel Stanley <joel@....id.au>
Subject: Re: [PATCH] ARM: dts: aspeed: yosemite4: adjust secondary flash name

On Tue, 2025-01-07 at 11:24 -0500, Patrick Williams wrote:
> On Tue, Jan 07, 2025 at 03:44:04PM +1030, Andrew Jeffery wrote:
> > 
> > >                 status = "okay";
> > >                 m25p,fast-read;
> > > -               label = "bmc2";
> > > +               label = "alt-bmc";
> > >                 spi-rx-bus-width = <4>;
> > >                 spi-max-frequency = <50000000>;
> > >         };
> > 
> > I'm hitting conflicts (?) when I apply this on top of[1]. Do you
> > mind
> > rebasing it?
> > 
> > [1]: https://github.com/amboar/linux/tree/for/bmc/aspeed/dt
> 
> Sure.  It looks like someone elsewhere changed the spi-rx-bus-width
> which is causing the conflict.  I'll resent a rebase.
> 
> I'd like this backported to the openbmc tree also.  Not sure which
> version is best for that tree right now.
> 

I've applied the rebased patch to both (the backport didn't conflict).

Andrew