From: Miquel Raynal <miquel.raynal@bootlin.com>
To: Jonathan Cameron <jic23@kernel.org>
Cc: linux-iio@vger.kernel.org, Lars-Peter Clausen <lars@metafoo.de>,
Thomas Petazzoni <thomas.petazzoni@bootlin.com>,
Alexandru Ardelean <ardeleanalex@gmail.com>,
Denis Ciocca <denis.ciocca@st.com>,
Linus Walleij <linus.walleij@linaro.org>,
Lorenzo Bianconi <lorenzo@kernel.org>,
christophe.priouzeau@st.com
Subject: Re: [PATCH v3 13/13] iio: core: Clarify the modes
Date: Mon, 11 Apr 2022 09:12:39 +0200 [thread overview]
Message-ID: <20220411091239.6a731790@xps13> (raw)
In-Reply-To: <20220410162741.71943665@jic23-huawei>
Hi Jonathan,
jic23@kernel.org wrote on Sun, 10 Apr 2022 16:27:41 +0100:
> On Tue, 5 Apr 2022 10:02:00 +0200
> Miquel Raynal <miquel.raynal@bootlin.com> wrote:
>
> > Hi Jonathan,
> >
> > miquel.raynal@bootlin.com wrote on Tue, 15 Mar 2022 16:44:50 +0100:
> >
> > > Hello,
> > >
> > > + Christophe
> > >
> > > jic23@kernel.org wrote on Sun, 27 Feb 2022 13:35:49 +0000:
> > >
> > > > On Mon, 14 Feb 2022 09:53:08 +0100
> > > > Miquel Raynal <miquel.raynal@bootlin.com> wrote:
> > > >
> > > > > Hi Jonathan,
> > > > >
> > > > > jic23@kernel.org wrote on Sun, 13 Feb 2022 18:42:24 +0000:
> > > > >
> > > > > > On Mon, 7 Feb 2022 15:38:40 +0100
> > > > > > Miquel Raynal <miquel.raynal@bootlin.com> wrote:
> > > > > >
> > > > > > > As part of a previous discussion with Jonathan Cameron [1], it appeared
> > > > > > > necessary to clarify the meaning of each mode so that new developers
> > > > > > > could understand better what they should use or not use and when.
> > > > > > >
> > > > > > > The idea of renaming these modes as been let aside because naming is a
> > > > > > > big deal and requires a lot of thinking. So for now let's focus on
> > > > > > > correctly explaining what each mode implies.
> > > > > > >
> > > > > > > [1] https://lore.kernel.org/linux-iio/20210930165510.2295e6c4@jic23-huawei/
> > > > > > >
> > > > > > > Suggested-by: Jonathan Cameron <jic23@kernel.org>
> > > > > > > Signed-off-by: Miquel Raynal <miquel.raynal@bootlin.com>
> > > > > > One trivial thing inline as a result of edits in v3.
> > > > > >
> > > > > > Otherwise, I want to let this series sit a little longer and ideally get
> > > > > > some eyes on the st_sensors patches.
> >
> > Sometimes there is no other choice than applying patches to get
> > feedback :) Hopefully nothing unexpected will happen, but as this
> > series lived almost two month on the mailing list already, I would
> > propose to merge the series as it is. We can still drop/revert it as we
> > are rather soon in the new cycle. If rebasing is needed just let me
> > know.
>
> Fully agree on pushing forwards with merging this. I've done the rebase whilst
> applying. Other than a bit of fuzz main change was that adxl367 made use
> of a kfifo buffer in the meantime so needed updating as well to drop the
> buffer type parameter.
Great!
> Take a quick look and see if I messed anything up.
> Applied to the togreg branch of iio.git and pushed out as testing for 0-day
> etc to take a poke at it before I make a mess of linux-next.
Yep, found on the testing branch, everything LGTM but TBH I don't fully
remember everything as it was "some" time ago :)
Thanks,
Miquèl
prev parent reply other threads:[~2022-04-11 7:12 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-07 14:38 [PATCH v3 00/13] Miscellaneous IIO core enhancements Miquel Raynal
2022-02-07 14:38 ` [PATCH v3 01/13] iio: core: Enhance the kernel doc of modes and currentmodes iio_dev entries Miquel Raynal
2022-02-07 14:38 ` [PATCH v3 02/13] iio: magnetometer: rm3100: Stop abusing the ->currentmode Miquel Raynal
2022-02-07 14:38 ` [PATCH v3 03/13] iio: adc: stm32-dfsdm: Avoid dereferencing ->currentmode Miquel Raynal
2022-02-07 14:38 ` [PATCH v3 04/13] iio: st_sensors: Return as early as possible from the _write_raw() callbacks Miquel Raynal
2022-02-07 14:38 ` [PATCH v3 05/13] iio: st_sensors: Drop the protection on _avail functions Miquel Raynal
2022-02-07 14:38 ` [PATCH v3 06/13] iio: st_sensors: Add a local lock for protecting odr Miquel Raynal
2022-02-07 14:38 ` [PATCH v3 07/13] iio: st_sensors: Stop abusing mlock to ensure internal coherency Miquel Raynal
2022-02-07 14:38 ` [PATCH v3 08/13] iio: st_sensors: Use iio_device_claim/release_direct_mode() when relevant Miquel Raynal
2022-02-07 14:38 ` [PATCH v3 09/13] iio: Un-inline iio_buffer_enabled() Miquel Raynal
2022-02-07 14:38 ` [PATCH v3 10/13] iio: core: Hide read accesses to iio_dev->currentmode Miquel Raynal
2022-02-07 14:38 ` [PATCH v3 11/13] iio: core: Move the currentmode entry to the opaque structure Miquel Raynal
2022-02-07 14:38 ` [PATCH v3 12/13] iio: core: Simplify the registration of kfifo buffers Miquel Raynal
2022-02-07 14:38 ` [PATCH v3 13/13] iio: core: Clarify the modes Miquel Raynal
2022-02-13 18:42 ` Jonathan Cameron
2022-02-14 8:53 ` Miquel Raynal
2022-02-27 13:35 ` Jonathan Cameron
2022-03-15 15:44 ` Miquel Raynal
2022-04-05 8:02 ` Miquel Raynal
2022-04-10 15:27 ` Jonathan Cameron
2022-04-11 7:12 ` Miquel Raynal [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=20220411091239.6a731790@xps13 \
--to=miquel.raynal@bootlin.com \
--cc=ardeleanalex@gmail.com \
--cc=christophe.priouzeau@st.com \
--cc=denis.ciocca@st.com \
--cc=jic23@kernel.org \
--cc=lars@metafoo.de \
--cc=linus.walleij@linaro.org \
--cc=linux-iio@vger.kernel.org \
--cc=lorenzo@kernel.org \
--cc=thomas.petazzoni@bootlin.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