From: Jonathan Cameron <jic23@kernel.org>
To: Crt Mori <cmo@melexis.com>
Cc: Andy Shevchenko <andriy.shevchenko@intel.com>,
Pengpeng Hou <pengpeng@iscas.ac.cn>,
David Lechner <dlechner@baylibre.com>,
Nuno Sa <nuno.sa@analog.com>, Andy Shevchenko <andy@kernel.org>,
linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org,
stable@vger.kernel.org
Subject: Re: [PATCH v2] iio: temperature: Build mlx90635 with CONFIG_MLX90635
Date: Wed, 1 Jul 2026 22:31:06 +0100 [thread overview]
Message-ID: <20260701223106.5ac21c5d@jic23-huawei> (raw)
In-Reply-To: <CAKv63uupUcUGXwXJQL957YtUmP+OZ5makvGROvFuvS8BWF-sPQ@mail.gmail.com>
On Thu, 25 Jun 2026 09:54:58 +0200
Crt Mori <cmo@melexis.com> wrote:
> Thanks for spotting this Pengpeng Hou; it's strange that nobody
> noticed until now. I would like to apologize to everyone for this
> mistake.
>
> Acked-by: Crt Mori <cmo@melexis.com>
Applied to the fixes-togreg branch of iio.git
Thanks
Jonathan
>
> On Thu, 25 Jun 2026 at 08:43, Andy Shevchenko
> <andriy.shevchenko@intel.com> wrote:
> >
> > On Thu, Jun 25, 2026 at 01:42:59PM +0800, Pengpeng Hou wrote:
> > > drivers/iio/temperature/Kconfig has a dedicated MLX90635 option, but
> > > the Makefile currently builds mlx90635.o under CONFIG_MLX90632.
> > >
> > > This means enabling CONFIG_MLX90635 alone does not carry its provider
> > > object into the build, while enabling CONFIG_MLX90632 unexpectedly also
> > > builds mlx90635.o.
> > >
> > > Gate mlx90635.o on the matching generated Kconfig symbol.
> >
> > Reviewed-by: Andy Shevchenko <andriy.shevchenko@intel.com>
> >
> > --
> > With Best Regards,
> > Andy Shevchenko
> >
> >
prev parent reply other threads:[~2026-07-01 21:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-24 8:13 [PATCH] iio: temperature: Build mlx90635 with CONFIG_MLX90635 Pengpeng Hou
2026-06-24 11:41 ` Andy Shevchenko
2026-06-25 5:42 ` [PATCH v2] " Pengpeng Hou
2026-06-25 6:43 ` Andy Shevchenko
2026-06-25 7:54 ` Crt Mori
2026-07-01 21:31 ` Jonathan Cameron [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=20260701223106.5ac21c5d@jic23-huawei \
--to=jic23@kernel.org \
--cc=andriy.shevchenko@intel.com \
--cc=andy@kernel.org \
--cc=cmo@melexis.com \
--cc=dlechner@baylibre.com \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nuno.sa@analog.com \
--cc=pengpeng@iscas.ac.cn \
--cc=stable@vger.kernel.org \
/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