linux-kernel - RE: [PATCH v1] ARM: dts: aspeed: yosemite4: Add i2c-mux for CPLD IOE on Spider Board

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:
 <TYZPR04MB5853B51141F3D0610D970265D66B2@TYZPR04MB5853.apcprd04.prod.outlook.com>
Date: Fri, 27 Sep 2024 09:24:11 +0000
From: Delphine_CC_Chiu/WYHQ/Wiwynn <Delphine_CC_Chiu@...ynn.com>
To: Andrew Jeffery <andrew@...econstruct.com.au>, Delphine_CC_Chiu/WYHQ/Wiwynn
	<Delphine_CC_Chiu@...ynn.com>, "patrick@...cx.xyz" <patrick@...cx.xyz>, Rob
 Herring <robh@...nel.org>, Krzysztof Kozlowski <krzk+dt@...nel.org>, Conor
 Dooley <conor+dt@...nel.org>, Joel Stanley <joel@....id.au>
CC: Ricky CX Wu <ricky.cx.wu.wiwynn@...il.com>, "devicetree@...r.kernel.org"
	<devicetree@...r.kernel.org>, "linux-arm-kernel@...ts.infradead.org"
	<linux-arm-kernel@...ts.infradead.org>, "linux-aspeed@...ts.ozlabs.org"
	<linux-aspeed@...ts.ozlabs.org>, "linux-kernel@...r.kernel.org"
	<linux-kernel@...r.kernel.org>
Subject: RE: [PATCH v1] ARM: dts: aspeed: yosemite4: Add i2c-mux for CPLD IOE
 on Spider Board



> -----Original Message-----
> From: Andrew Jeffery <andrew@...econstruct.com.au>
> Sent: Friday, September 27, 2024 1:57 PM
> To: Delphine_CC_Chiu/WYHQ/Wiwynn <Delphine_CC_Chiu@...ynn.com>;
> patrick@...cx.xyz; Rob Herring <robh@...nel.org>; Krzysztof Kozlowski
> <krzk+dt@...nel.org>; Conor Dooley <conor+dt@...nel.org>; Joel Stanley
> <joel@....id.au>
> Cc: Ricky CX Wu <ricky.cx.wu.wiwynn@...il.com>;
> devicetree@...r.kernel.org; linux-arm-kernel@...ts.infradead.org;
> linux-aspeed@...ts.ozlabs.org; linux-kernel@...r.kernel.org
> Subject: Re: [PATCH v1] ARM: dts: aspeed: yosemite4: Add i2c-mux for CPLD
> IOE on Spider Board
> 
>  [External Sender]
> 
>  [External Sender]
> 
> On Thu, 2024-09-26 at 10:41 +0800, Delphine CC Chiu wrote:
> > From: Ricky CX Wu <ricky.cx.wu.wiwynn@...il.com>
> >
> > Add I2C mux for CPLD IOE on Spider Board.
> >
> > Signed-off-by: Ricky CX Wu <ricky.cx.wu.wiwynn@...il.com>
> > Signed-off-by: Delphine CC Chiu <Delphine_CC_Chiu@...ynn.com>
> > ---
> >  .../aspeed/aspeed-bmc-facebook-yosemite4.dts  | 67
> > +++++++++++++++++++
> >  1 file changed, 67 insertions(+)
> >
> > diff --git
> > a/arch/arm/boot/dts/aspeed/aspeed-bmc-facebook-yosemite4.dts
> > b/arch/arm/boot/dts/aspeed/aspeed-bmc-facebook-yosemite4.dts
> > index 98477792aa00..ea1a9c765483 100644
> > --- a/arch/arm/boot/dts/aspeed/aspeed-bmc-facebook-yosemite4.dts
> > +++ b/arch/arm/boot/dts/aspeed/aspeed-bmc-facebook-yosemite4.dts
> > @@ -17,6 +17,9 @@ aliases {
> >               serial6 = &uart7;
> >               serial7 = &uart8;
> >               serial8 = &uart9;
> > +
> > +             i2c28 = &imux28;
> > +             i2c29 = &imux29;
> >       };
> >
> 
> Have you tried to apply all of your individual yosemite4 patches together in
> one branch? I have, and unfortunately I can't apply them all, because they
> generate conflicts with each other.
> 
> If your patches have context dependencies you need to send them as a single
> series and not separate patches that cannot be properly combined.
> 
> Please assess the remaining yosemite4 devicetree patches (those you haven't
> received a thank-you email for) and send an appropriately constructed series
> so they can all be applied together, based on the tree here:
> 
> https://urldefense.com/v3/__https://github.com/amboar/linux/tree/for/bmc/d
> t__;!!J63qqgXj!KnZT-wO8ksK53BvGiFMdhhNgCnQ98FQLMdHeyYOSGsPw2KG1
> MNeJjvsZz4zuX7YegeuLfSsa9q9ZEBriDYsTTu8LjuM$
> 
> Please also indicate in the cover letter (with links to lore) which remaining
> patches are truly independent that still need to be applied.
> 
> Thanks,
> 
> Andrew
Hi Andrew

Would like to ask should I base on the openbmc/linux repo to create the
remaining patches that have context dependencies and add the lore link
of the those patches that I've sent in the cover letter?

Ricky