linux-kernel - Re: [PATCH v6 2/2] ARM: dts: aspeed: sbp1: IBM sbp1 BMC 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] [thread-next>] [day] [month] [year] [list]

Message-ID: <9e9bf461b2ef8993bb46206b3cdf40806a528856.camel@codeconstruct.com.au>
Date: Wed, 06 Nov 2024 09:51:10 +1030
From: Andrew Jeffery <andrew@...econstruct.com.au>
To: Guenter Roeck <linux@...ck-us.net>, Naresh Solanki
	 <naresh.solanki@...ements.com>
Cc: robh@...nel.org, krzk+dt@...nel.org, conor+dt@...nel.org, 
 devicetree@...r.kernel.org, linux-kernel@...r.kernel.org,
 jdelvare@...e.com,  sylv@...v.io, linux-hwmon@...r.kernel.org, Joel Stanley
 <joel@....id.au>,  Patrick Rudolph <patrick.rudolph@...ements.com>,
 linux-arm-kernel@...ts.infradead.org,  linux-aspeed@...ts.ozlabs.org
Subject: Re: [PATCH v6 2/2] ARM: dts: aspeed: sbp1: IBM sbp1 BMC board

On Tue, 2024-11-05 at 07:47 -0800, Guenter Roeck wrote:
> On 11/4/24 20:10, Naresh Solanki wrote:
> [ ... ]
> 
> > >  From a spot check, the warnings seem legitimate. Did you send
> > > the right
> > > patches?
> > Just checked again. They are resolved. But I guess the dtbinding
> > patch
> > for the above warning are merged in hwmon-next branch & not in
> > dt/next
> > 
> 
> Did I apply some patches which should have been applied elsewhere ?
> 
> If so, please let me know, and I'll drop them.

No need to drop anything for now: It was just that bindings for some
hwmon devices defined in hwmon-next are used in Naresh's devicetree
here.

Merging hwmon-next and applying his patches resolves my concerns.

Unless anyone feels otherwise, I expect we can can carry on
independently with the understanding it will be resolved in the same
way at the next rc1 (barring any other concerns with Naresh's patches).

Andrew