From: Andy Shevchenko <andriy.shevchenko@intel.com>
To: Shrikant <raskar.shree97@gmail.com>
Cc: "Jonathan Cameron" <jic23@kernel.org>,
"David Lechner" <dlechner@baylibre.com>,
"Nuno Sá" <nuno.sa@analog.com>,
"Andy Shevchenko" <andy@kernel.org>,
"Rob Herring" <robh@kernel.org>,
"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
"Conor Dooley" <conor+dt@kernel.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 v4 4/4] iio: proximity: rfd77402: Add interrupt handling support
Date: Tue, 6 Jan 2026 22:47:17 +0200 [thread overview]
Message-ID: <aV101TrC5hB_nHJM@smile.fi.intel.com> (raw)
In-Reply-To: <CAHc1_P4dCdt6QFgfZ8OUZGT+UfLqiP_ect7pOsd_HeQaDe8jTg@mail.gmail.com>
On Tue, Jan 06, 2026 at 05:39:29AM +0530, Shrikant wrote:
...
> > > #include <linux/module.h>
> > > #include <linux/i2c.h>
> > > #include <linux/delay.h>
> > > +#include <linux/interrupt.h>
> > > +#include <linux/completion.h>
> > > #include <linux/iopoll.h>
> >
> > Same comment as per previous patch. Do not add even more misordering, please.
> Will it be okay if I re-order the includes as below ?
> #include <linux/completion.h>
> #include <linux/delay.h>
> #include <linux/i2c.h>
> #include <linux/interrupt.h>
> #include <linux/iopoll.h>
> #include <linux/module.h>
Just try to squeeze the new inclusions in the longest chain of the sorted ones
(yes, some original ones may be left untouched and hence unordered).
> #include <linux/iio/iio.h>
...
> > > +/**
> > > + * struct rfd77402_data - device-specific data for the RFD77402 sensor
> > > + * @client: I2C client handle
> > > + * @lock: mutex to serialize sensor reads
> > > + * @completion: completion used for interrupt-driven measurements
> > > + * @irq_en: indicates whether interrupt mode is enabled
> > > + */
> > > struct rfd77402_data {
> > > struct i2c_client *client;
> > > - /* Serialize reads from the sensor */
> > > struct mutex lock;
> > > + struct completion completion;
> > > + bool irq_en;
> > > };
> >
> > The kernel-doc conversion can be a separate patch, but I'm not insisting.
> I can split this into a separate patch within the same series.
> Please let me know if you would prefer it to be handled differently.
It's up to maintainers.
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2026-01-06 20:47 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-01 16:17 [PATCH v4 0/4] iio: proximity: Add interrupt support for RFD77402 Shrikant Raskar via B4 Relay
2026-01-01 16:17 ` [PATCH v4 1/4] dt-bindings: iio: proximity: Add RF Digital RFD77402 ToF sensor Shrikant Raskar via B4 Relay
2026-01-11 12:39 ` Jonathan Cameron
2026-01-01 16:17 ` [PATCH v4 2/4] iio: proximity: rfd77402: Add OF device ID for enumeration via DT Shrikant Raskar via B4 Relay
2026-01-01 16:17 ` [PATCH v4 3/4] iio: proximity: rfd77402: Use kernel helper for result polling Shrikant Raskar via B4 Relay
2026-01-02 12:24 ` Andy Shevchenko
2026-01-01 16:17 ` [PATCH v4 4/4] iio: proximity: rfd77402: Add interrupt handling support Shrikant Raskar via B4 Relay
2026-01-02 12:34 ` Andy Shevchenko
2026-01-06 0:09 ` Shrikant
2026-01-06 20:47 ` Andy Shevchenko [this message]
2026-01-11 12:36 ` Jonathan Cameron
2026-01-11 12:49 ` Jonathan Cameron
2026-01-02 12:26 ` [PATCH v4 0/4] iio: proximity: Add interrupt support for RFD77402 Andy Shevchenko
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=aV101TrC5hB_nHJM@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=jic23@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox