From: "Arnd Bergmann" <arnd@arndb.de>
To: "Heiner Kallweit" <hkallweit1@gmail.com>,
"Arnd Bergmann" <arnd@kernel.org>,
"Andi Shyti" <andi.shyti@kernel.org>,
"Wim Van Sebroeck" <wim@linux-watchdog.org>,
"Guenter Roeck" <linux@roeck-us.net>,
"Wolfram Sang" <wsa+renesas@sang-engineering.com>
Cc: "Jarkko Nikula" <jarkko.nikula@linux.intel.com>,
"Geert Uytterhoeven" <geert+renesas@glider.be>,
"Jean Delvare" <jdelvare@suse.de>,
linux-i2c@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-watchdog@vger.kernel.org
Subject: Re: [PATCH] i2c: i801: add I2C_MUX dependency
Date: Fri, 05 Apr 2024 22:16:30 +0200 [thread overview]
Message-ID: <4b38f876-2178-458e-9e47-c436b5cd7eab@app.fastmail.com> (raw)
In-Reply-To: <35e0b5cf-f7d8-4329-8dba-1098ed9451dd@gmail.com>
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
next prev parent reply other threads:[~2024-04-05 20:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-05 14:27 [PATCH] i2c: i801: add I2C_MUX dependency Arnd Bergmann
2024-04-05 19:18 ` Heiner Kallweit
2024-04-05 20:16 ` Arnd Bergmann [this message]
2024-04-06 0:31 ` Andi Shyti
2024-04-06 13:08 ` Guenter Roeck
2024-04-06 15:45 ` Arnd Bergmann
2024-04-08 11:42 ` Guenter Roeck
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4b38f876-2178-458e-9e47-c436b5cd7eab@app.fastmail.com \
--to=arnd@arndb.de \
--cc=andi.shyti@kernel.org \
--cc=arnd@kernel.org \
--cc=geert+renesas@glider.be \
--cc=hkallweit1@gmail.com \
--cc=jarkko.nikula@linux.intel.com \
--cc=jdelvare@suse.de \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-watchdog@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=wim@linux-watchdog.org \
--cc=wsa+renesas@sang-engineering.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).