From: Matti Vaittinen <mazziesaccount@gmail.com>
To: Jonathan Cameron <jic23@kernel.org>,
Chenyuan Yang <chenyuan0y@gmail.com>
Cc: lars@metafoo.de, linux-iio@vger.kernel.org
Subject: Re: [PATCH] iio: Fix the sorting functionality in iio_gts_build_avail_time_table
Date: Thu, 14 Mar 2024 19:05:31 +0200 [thread overview]
Message-ID: <bd4e9aa4-71cd-4e29-a4e7-e00ad0732a7d@gmail.com> (raw)
In-Reply-To: <20240314153656.493ee487@jic23-huawei>
On 3/14/24 17:36, Jonathan Cameron wrote:
> On Wed, 13 Mar 2024 10:57:35 -0500
> Chenyuan Yang <chenyuan0y@gmail.com> wrote:
>
>> The sorting in iio_gts_build_avail_time_table is not working as intended.
> For function names, add () so
> The sorting in iio_gts_build_avail_time_table() is not working as intended.
>
> I can fix this up whilst applying but will be waiting for a RB or related
> from Matti before queuing this up.
Thanks for waiting Jonathan. I wanted to run a set of tests before
acking this - but I didn't manage to find the required half an hour for
it Today... I'll handle this early tomorrow.
> I'm assuming there are no existing drivers in tree that hit this problem?
I don't think so. The ROHM drivers which use the avail_times have (by
luck) the time tables already sorted in a suitable way.
> If there are reply saying which ones so I can assess whether to rush this
> fix in or not.
>
> Thanks,
>
> Jonathan
>
Yours,
-- Matti
--
Matti Vaittinen
Linux kernel developer at ROHM Semiconductors
Oulu Finland
~~ When things go utterly wrong vim users can always type :help! ~~
next prev parent reply other threads:[~2024-03-14 17:05 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-13 15:57 [PATCH] iio: Fix the sorting functionality in iio_gts_build_avail_time_table Chenyuan Yang
2024-03-14 15:36 ` Jonathan Cameron
2024-03-14 17:05 ` Matti Vaittinen [this message]
2024-03-15 7:55 ` Matti Vaittinen
2024-03-15 20:49 ` Chenyuan Yang
2024-03-16 13:40 ` Jonathan Cameron
2024-03-20 7:02 ` Matti Vaittinen
2024-03-23 18:13 ` Jonathan Cameron
2024-04-11 12:19 ` Matti Vaittinen
2024-04-26 5:52 ` Matti Vaittinen
2024-04-28 16:57 ` 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=bd4e9aa4-71cd-4e29-a4e7-e00ad0732a7d@gmail.com \
--to=mazziesaccount@gmail.com \
--cc=chenyuan0y@gmail.com \
--cc=jic23@kernel.org \
--cc=lars@metafoo.de \
--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