linux-kernel - Re: [PATCH] i2c: i801: add I2C

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: <4b38f876-2178-458e-9e47-c436b5cd7eab@app.fastmail.com>
Date: Fri, 05 Apr 2024 22:16:30 +0200
From: "Arnd Bergmann" <arnd@...db.de>
To: "Heiner Kallweit" <hkallweit1@...il.com>,
 "Arnd Bergmann" <arnd@...nel.org>, "Andi Shyti" <andi.shyti@...nel.org>,
 "Wim Van Sebroeck" <wim@...ux-watchdog.org>,
 "Guenter Roeck" <linux@...ck-us.net>,
 "Wolfram Sang" <wsa+renesas@...g-engineering.com>
Cc: "Jarkko Nikula" <jarkko.nikula@...ux.intel.com>,
 "Geert Uytterhoeven" <geert+renesas@...der.be>,
 "Jean Delvare" <jdelvare@...e.de>, linux-i2c@...r.kernel.org,
 linux-kernel@...r.kernel.org, linux-watchdog@...r.kernel.org
Subject: Re: [PATCH] i2c: i801: add I2C_MUX dependency

On Fri, Apr 5, 2024, at 21:18, Heiner Kallweit wrote:
> On 05.04.2024 16:27, Arnd Bergmann wrote:
>
> Question is whether we really want that I2C_MUX restricts the choice for
> I2C_I801. Alternatively we can skip building the mux part in the 
> problem case.
> The mux part can be used on very few old Asus systems with > 8 memory 
> slots only.
> Proposal I sent:
> https://lore.kernel.org/all/4dhfyaefnw2rtx5q7aaum6pfwha5o3vs65iqcrj2ghps34ubtw@b3bw3gggudjs/T/
>
> Note also the CI bot tags, as the problem was reported by a CI bot before.

That seems fine to me as well, and it avoids having to mess with
the watchdog driver. We may want to change that bit anyway, but
then it can be done independently.

     Arnd