From: "Ardelean, Alexandru" <alexandru.Ardelean@analog.com>
To: "jic23@kernel.org" <jic23@kernel.org>,
"denis.ciocca@st.com" <denis.ciocca@st.com>,
"linux-iio@vger.kernel.org" <linux-iio@vger.kernel.org>
Subject: Re: [PATCH 0/5] move buffer allocation into st_sensors_buffer
Date: Thu, 1 Aug 2019 08:23:50 +0000 [thread overview]
Message-ID: <caa578445e0442c75f1c55aff656aa6e2dfd89e6.camel@analog.com> (raw)
In-Reply-To: <20190731215250.16403-1-denis.ciocca@st.com>
On Wed, 2019-07-31 at 14:52 -0700, Denis Ciocca wrote:
> [External]
>
> As proposed by Alexandru, memory allocation and de-allocation can be
> performed in a more neat way in st_sensors_buffer.
>
Thank you for this series as well.
As a note: I think this depends on the previous series: "[PATCH v2 0/4] preenable/postenable/predisable fixup for ST
drivers"
The changeset looks neat.
Alex
> Denis Ciocca (5):
> iio:common: introduce st_sensors_buffer_preenable/predisable functions
> iio:accel: do not allocate/de-allocate buffer here but link setup_ops
> to st_sensors_buffer
> iio:gyro: do not allocate/de-allocate buffer here but link setup_ops
> to st_sensors_buffer
> iio:magn: do not allocate/de-allocate buffer here but link setup_ops
> to st_sensors_buffer
> iio:pressure: do not allocate/de-allocate buffer here but link
> setup_ops to st_sensors_buffer
>
> drivers/iio/accel/st_accel_buffer.c | 14 +++---------
> .../iio/common/st_sensors/st_sensors_buffer.c | 22 +++++++++++++++++++
> drivers/iio/gyro/st_gyro_buffer.c | 14 +++---------
> drivers/iio/magnetometer/st_magn_buffer.c | 14 +++---------
> drivers/iio/pressure/st_pressure_buffer.c | 14 +++---------
> include/linux/iio/common/st_sensors.h | 2 ++
> 6 files changed, 36 insertions(+), 44 deletions(-)
>
prev parent reply other threads:[~2019-08-01 8:23 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-31 21:52 [PATCH 0/5] move buffer allocation into st_sensors_buffer Denis Ciocca
2019-07-31 21:52 ` [PATCH 1/5] iio:common: introduce st_sensors_buffer_preenable/predisable functions Denis Ciocca
2019-08-01 8:24 ` Ardelean, Alexandru
2019-08-05 15:21 ` Jonathan Cameron
2019-08-05 15:35 ` Jonathan Cameron
2019-08-05 17:18 ` Denis CIOCCA
2019-08-05 17:40 ` Denis CIOCCA
2019-07-31 21:52 ` [PATCH 2/5] iio:accel: do not allocate/de-allocate buffer here but link setup_ops to st_sensors_buffer Denis Ciocca
2019-08-01 8:24 ` Ardelean, Alexandru
2019-07-31 21:52 ` [PATCH 3/5] iio:gyro: " Denis Ciocca
2019-08-01 8:25 ` Ardelean, Alexandru
2019-07-31 21:52 ` [PATCH 4/5] iio:magn: " Denis Ciocca
2019-08-01 8:25 ` Ardelean, Alexandru
2019-07-31 21:52 ` [PATCH 5/5] iio:pressure: " Denis Ciocca
2019-08-01 8:25 ` Ardelean, Alexandru
2019-08-01 8:23 ` Ardelean, Alexandru [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=caa578445e0442c75f1c55aff656aa6e2dfd89e6.camel@analog.com \
--to=alexandru.ardelean@analog.com \
--cc=denis.ciocca@st.com \
--cc=jic23@kernel.org \
--cc=linux-iio@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;
as well as URLs for NNTP newsgroup(s).