From: "Arnd Bergmann" <arnd@arndb.de>
To: "Guenter Roeck" <linux@roeck-us.net>,
"Arnd Bergmann" <arnd@kernel.org>,
"Alexandre Belloni" <alexandre.belloni@bootlin.com>,
"Jonathan Cameron" <jic23@kernel.org>,
"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
"Frank Li" <Frank.Li@nxp.com>,
"Andy Shevchenko" <andriy.shevchenko@intel.com>,
"Carlos Song" <carlos.song@nxp.com>,
"Adrian Fluturel" <fluturel.adrian@gmail.com>
Cc: "David Lechner" <dlechner@baylibre.com>,
"Nuno Sá" <nuno.sa@analog.com>,
"Andy Shevchenko" <andy@kernel.org>,
linux-hwmon@vger.kernel.org, linux-kernel@vger.kernel.org,
"linux-i3c@lists.infradead.org" <linux-i3c@lists.infradead.org>,
linux-iio@vger.kernel.org
Subject: Re: [PATCH] i3c, iio: fix i3c driver dependencies
Date: Mon, 02 Feb 2026 17:04:32 +0100 [thread overview]
Message-ID: <01676354-a42d-4862-87d9-7377ea55fae8@app.fastmail.com> (raw)
In-Reply-To: <8daadfff-a8c8-4775-93de-72088f929f9f@roeck-us.net>
On Mon, Feb 2, 2026, at 16:24, Guenter Roeck wrote:
> On 2/2/26 01:55, Arnd Bergmann wrote:
>> @@ -2381,19 +2380,7 @@ config SENSORS_TMP102
>>
>> config SENSORS_TMP103
>> tristate "Texas Instruments TMP103"
>> - depends on I2C
>> - select REGMAP_I2C
>> - help
>> - If you say yes here you get support for Texas Instruments TMP103
>> - sensor chips.
>> -
>> - This driver can also be built as a module. If so, the module
>> - will be called tmp103.
>>
>
> Why ? That doesn't make sense to me, and if it does, it seems unrelated
> to what this patch claims to do.
Indeed, that was not intended here. Sending a fixed version now.
I have no idea how that change got in there.
Arnd
prev parent reply other threads:[~2026-02-02 16:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-02 9:55 Arnd Bergmann
2026-02-02 15:24 ` Guenter Roeck
2026-02-02 16:04 ` Arnd Bergmann [this message]
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=01676354-a42d-4862-87d9-7377ea55fae8@app.fastmail.com \
--to=arnd@arndb.de \
--cc=Frank.Li@nxp.com \
--cc=alexandre.belloni@bootlin.com \
--cc=andriy.shevchenko@intel.com \
--cc=andy@kernel.org \
--cc=arnd@kernel.org \
--cc=carlos.song@nxp.com \
--cc=dlechner@baylibre.com \
--cc=fluturel.adrian@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=jic23@kernel.org \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux-i3c@lists.infradead.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=nuno.sa@analog.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
all inboxes | Powered by JetHome®