linux-kernel - Re: [PATCH dev 6.6 v3] ARM: dts: aspeed: yosemite4: add I3C config in DTS

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: <047ea26fbb5713e852431d0731e21d34af39e1c2.camel@codeconstruct.com.au>
Date: Mon, 17 Feb 2025 11:31:23 +1030
From: Andrew Jeffery <andrew@...econstruct.com.au>
To: MarshallZhan-wiwynn <marshall_zhan@...ynn.com>, 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 dev 6.6 v3] ARM: dts: aspeed: yosemite4: add I3C config
 in DTS

On Mon, 2025-02-17 at 11:14 +1030, Andrew Jeffery wrote:
> Hi Marshall,
> 
> On Fri, 2025-02-14 at 09:15 +0800, MarshallZhan-wiwynn wrote:
> > Set I3C config in yosemite4 DTS.
> > 
> > Test plan:
> > Tested pass with aspeed I3C patches and I3C hub driver.
> 
> Can you please expand the commit message to provide details? This
> statement is quite vague, and I don't find it terribly helpful as it
> stands. Which aspeed patches? What tests?

Also, you've sent this patch to the upstream lists and maintainers, but
it appears you're intending this to be applied to the OpenBMC kernel
fork. Please understand the difference between the two and review my
recent response to Rush Chen:

https://lore.kernel.org/all/9f0447151e6574d74e7fa9cbbb50d8e970059273.camel@codeconstruct.com.au/

Beyond that, for patches to be backported into the OpenBMC fork they
should first be merged upstream, in which case they must be tested
against a recent upstream tag (e.g. v6.14-r3) before they are sent. It
will be worth reviewing the following:

https://docs.kernel.org/process/development-process.html

The "Submitting Patches" documentation provides a more succinct
treatment:

https://docs.kernel.org/process/submitting-patches.html

If you have any questions, please feel free to contact myself or Joel
off-list.

Andrew