From: Andy Shevchenko <andriy.shevchenko@intel.com>
To: Jonathan Cameron <jic23@kernel.org>
Cc: Shrikant Raskar <raskar.shree97@gmail.com>,
robh@kernel.org, krzk+dt@kernel.org, conor+dt@kernel.org,
dlechner@baylibre.com, nuno.sa@analog.com, andy@kernel.org,
heiko@sntech.de, neil.armstrong@linaro.org,
skhan@linuxfoundation.org, david.hunter.linux@gmail.com,
linux-iio@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 0/4] iio: proximity: Add interrupt support for RFD77402
Date: Sun, 28 Dec 2025 19:24:16 +0200 [thread overview]
Message-ID: <aVFnwACvU_GJAFqs@smile.fi.intel.com> (raw)
In-Reply-To: <20251227174559.33539640@jic23-huawei>
On Sat, Dec 27, 2025 at 05:45:59PM +0000, Jonathan Cameron wrote:
> On Sun, 21 Dec 2025 14:08:58 +0530
> Shrikant Raskar <raskar.shree97@gmail.com> wrote:
>
> > This patch series adds:
> > - Add RF Digital vendor prefix
> > - YAML binding for RFD77402
> > - Add OF device ID for enumeration via DT
> > - Use kernel helper for result polling
> > - Interrupt handling support
> >
> > These changes enable DT-based configuration and event-driven
> > operation for the RFD77402 Time-of-Flight sensor.
>
> Hi Shrikant,
>
> I'm only seeing this cover letter (and lore doesn't seem
> to have the patches either). Probably need to resend them.
Same to me, please, figure out what's wrong and next time sent proper v4
to avoid confusion.
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2025-12-28 17:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-21 8:38 [PATCH v3 0/4] iio: proximity: Add interrupt support for RFD77402 Shrikant Raskar
2025-12-27 17:45 ` Jonathan Cameron
2025-12-28 17:24 ` Andy Shevchenko [this message]
2025-12-29 18:45 ` Shrikant
2025-12-31 17:08 ` Jonathan Cameron
2026-01-01 16:25 ` Shrikant
-- strict thread matches above, loose matches on Subject: below --
2025-12-25 9:25 Shrikant Raskar
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=aVFnwACvU_GJAFqs@smile.fi.intel.com \
--to=andriy.shevchenko@intel.com \
--cc=andy@kernel.org \
--cc=conor+dt@kernel.org \
--cc=david.hunter.linux@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=dlechner@baylibre.com \
--cc=heiko@sntech.de \
--cc=jic23@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=neil.armstrong@linaro.org \
--cc=nuno.sa@analog.com \
--cc=raskar.shree97@gmail.com \
--cc=robh@kernel.org \
--cc=skhan@linuxfoundation.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 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.