From: Lars-Peter Clausen <lars@metafoo.de>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Cc: Jonathan Cameron <Jonathan.Cameron@huawei.com>,
linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org,
Jonathan Cameron <jic23@kernel.org>,
Michael Hennerich <michael.hennerich@analog.com>
Subject: Re: [PATCH v1 1/2] iio: core: Replace iio_sysfs_match_string_with_gaps() by __sysfs_match_string()
Date: Wed, 18 Jan 2023 08:37:01 -0800 [thread overview]
Message-ID: <64406c4f-c9da-b434-360b-1050ff685d2d@metafoo.de> (raw)
In-Reply-To: <Y8gVDs0UoiHqCRsM@smile.fi.intel.com>
On 1/18/23 07:49, Andy Shevchenko wrote:
> On Wed, Jan 18, 2023 at 07:22:30AM -0800, Lars-Peter Clausen wrote:
>> On 1/17/23 23:48, Andy Shevchenko wrote:
>>> None of the current users is using gaps in the list of the items.
>>> No need to have a specific function for that, just replace it by
>>> library available __sysfs_match_string().
>> Hm, I specifically remember adding this for a driver where there were gaps.
>> One of the DACs. But it might be that the driver itself never made it
>> upstream.
> I have checked all modules that have struct iio_enum and/or ("or" probably may
> not happen) IIO_ENUM() in them.
>
> It might be that I missed something.
I checked too, I can't find it either. The driver probably never made it
upstream.
next prev parent reply other threads:[~2023-01-18 16:37 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-18 7:48 Andy Shevchenko
2023-01-18 7:48 ` [PATCH v1 2/2] iio: core: Sort headers Andy Shevchenko
2023-01-18 15:22 ` [PATCH v1 1/2] iio: core: Replace iio_sysfs_match_string_with_gaps() by __sysfs_match_string() Lars-Peter Clausen
2023-01-18 15:49 ` Andy Shevchenko
2023-01-18 16:37 ` Lars-Peter Clausen [this message]
2023-01-19 8:00 ` Nuno Sá
2023-01-19 11:23 ` Andy Shevchenko
2023-01-19 13:24 ` Nuno Sá
2023-01-21 17:49 ` Jonathan Cameron
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=64406c4f-c9da-b434-360b-1050ff685d2d@metafoo.de \
--to=lars@metafoo.de \
--cc=Jonathan.Cameron@huawei.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=jic23@kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=michael.hennerich@analog.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
all inboxes | Powered by JetHome®