From: Andy Shevchenko <andriy.shevchenko@intel.com>
To: NanamiKite <nanami@yosoro.hk>
Cc: "Jonathan Cameron" <jic23@kernel.org>,
"David Lechner" <dlechner@baylibre.com>,
"Nuno Sá" <nuno.sa@analog.com>,
"Andy Shevchenko" <andy@kernel.org>,
"Hans de Goede" <hansg@kernel.org>,
linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] iio: light: cm32181: Add support for CM32183
Date: Thu, 19 Nov 2026 11:06:43 +0200 [thread overview]
Message-ID: <av68I02S8S5aa9zb@ashevche-desk.local> (raw)
In-Reply-To: <tencent_84B150942865006BA546B43E5026951EA005@qq.com>
On Thu, Nov 19, 2026 at 10:33:00AM +0800, NanamiKite wrote:
> On Thu, 19 Nov 2026 01:44:05 +0000
> Jonathan Cameron <jic23@kernel.org> wrote:
>
> > Take a look at linux-next or the iio.git tree on kernel.org. Or indeed sanity check the list.
> > https://lore.kernel.org/all/tencent_850445458D21608E9C8821E6728457F31C0A@qq.com/
> > Pretty unlucky to hit same thing that was added about 2 weeks ago. I guess that device is proving popular!
>
> Thanks for the pointer, and sorry for the noise! I'll make sure to check
> iio.git / linux-next first next time.
>
> Haha, it's actually quite a niche device -- I just picked one up
> secondhand to replace my old Surface Go 2 for development work, so I
> definitely didn't expect someone else to have already sent the exact
> same patch two weeks ago!
Linux on Microsoft Surface devices has a mature and active community.
Even I used to have Microsoft Surface Book 1 at some point... :-)
--
With Best Regards,
Andy Shevchenko
prev parent reply other threads:[~2026-11-19 9:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-18 15:11 [PATCH] iio: light: cm32181: Add support for CM32183 NanamiKite
2026-11-18 15:18 ` Joshua Crofts
2026-11-18 15:42 ` Hans de Goede
2026-11-19 1:44 ` Jonathan Cameron
2026-11-19 2:33 ` NanamiKite
2026-11-19 9:06 ` Andy Shevchenko [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=av68I02S8S5aa9zb@ashevche-desk.local \
--to=andriy.shevchenko@intel.com \
--cc=andy@kernel.org \
--cc=dlechner@baylibre.com \
--cc=hansg@kernel.org \
--cc=jic23@kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nanami@yosoro.hk \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.