From: Jonathan Cameron <jic23@kernel.org>
To: Christophe JAILLET <christophe.jaillet@wanadoo.fr>
Cc: Lars-Peter Clausen <lars@metafoo.de>,
linux-kernel@vger.kernel.org, kernel-janitors@vger.kernel.org,
linux-iio@vger.kernel.org
Subject: Re: [PATCH] iio: buffer: Use IIO_SEPARATE instead of a hard-coded 0
Date: Thu, 21 Dec 2023 10:49:40 +0000 [thread overview]
Message-ID: <20231221104940.7e9d7b0f@jic23-huawei> (raw)
In-Reply-To: <1d17f57423172fcb9d9797cfe7c8282f356049c2.1702831285.git.christophe.jaillet@wanadoo.fr>
On Sun, 17 Dec 2023 17:41:45 +0100
Christophe JAILLET <christophe.jaillet@wanadoo.fr> wrote:
> Use an explicit IIO_SEPARATE instead of 0 for the 'shared_by' parameter
> when calling __iio_add_chan_devattr().
>
> For some reason, commit 3704432fb1fd ("iio: refactor info mask and ext_info
> attribute creation.") updated only 1 place out of 4.
> Update the remaining ones now.
>
> Signed-off-by: Christophe JAILLET <christophe.jaillet@wanadoo.fr>
Makes sense
Applied to the togreg branch of iio.git.
It's fairly unlikely I'll get another pull request out unless the final
6.7 release isn't until after the new year for some reason.
As such, this is probably now 6.9 material
Thanks,
Jonathan
> ---
> drivers/iio/industrialio-buffer.c | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/iio/industrialio-buffer.c b/drivers/iio/industrialio-buffer.c
> index 09c41e9ccf87..b581a7e80566 100644
> --- a/drivers/iio/industrialio-buffer.c
> +++ b/drivers/iio/industrialio-buffer.c
> @@ -616,7 +616,7 @@ static int iio_buffer_add_channel_sysfs(struct iio_dev *indio_dev,
> &iio_show_fixed_type,
> NULL,
> 0,
> - 0,
> + IIO_SEPARATE,
> &indio_dev->dev,
> buffer,
> &buffer->buffer_attr_list);
> @@ -629,7 +629,7 @@ static int iio_buffer_add_channel_sysfs(struct iio_dev *indio_dev,
> &iio_scan_el_show,
> &iio_scan_el_store,
> chan->scan_index,
> - 0,
> + IIO_SEPARATE,
> &indio_dev->dev,
> buffer,
> &buffer->buffer_attr_list);
> @@ -639,7 +639,7 @@ static int iio_buffer_add_channel_sysfs(struct iio_dev *indio_dev,
> &iio_scan_el_ts_show,
> &iio_scan_el_ts_store,
> chan->scan_index,
> - 0,
> + IIO_SEPARATE,
> &indio_dev->dev,
> buffer,
> &buffer->buffer_attr_list);
prev parent reply other threads:[~2023-12-21 10:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-17 16:41 [PATCH] iio: buffer: Use IIO_SEPARATE instead of a hard-coded 0 Christophe JAILLET
2023-12-21 10:49 ` Jonathan Cameron [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=20231221104940.7e9d7b0f@jic23-huawei \
--to=jic23@kernel.org \
--cc=christophe.jaillet@wanadoo.fr \
--cc=kernel-janitors@vger.kernel.org \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@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