From: Vasileios Amoiridis <vassilisamir@gmail.com>
To: Matti Vaittinen <mazziesaccount@gmail.com>
Cc: Vasileios Amoiridis <vassilisamir@gmail.com>,
Lars-Peter Clausen <lars@metafoo.de>,
jic23@kernel.org, linux-iio@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1 0/2] iio: core: remove iio_validate_own_trigger() function
Date: Sun, 22 Sep 2024 13:07:21 +0200 [thread overview]
Message-ID: <20240922110721.GA439861@vamoiridPC> (raw)
In-Reply-To: <609fdda9-fcf4-426f-84c8-411a59ed5fab@gmail.com>
On Sun, Sep 22, 2024 at 12:44:15PM +0300, Matti Vaittinen wrote:
> On 9/21/24 23:07, Vasileios Amoiridis wrote:
> > On Sat, Sep 21, 2024 at 12:23:39PM -0700, Lars-Peter Clausen wrote:
> > > On 9/21/24 11:19, Vasileios Amoiridis wrote:
> > > > The iio_validate_own_trigger() function was added in this commit [1] but it is
> > > > the same with the below function called iio_trigger_validate_own_device(). The
> > > > bodies of the functions can be found in [2], [3].
> > > >
> > > > [1]: https://lore.kernel.org/all/51cd3e3e74a6addf8d333f4a109fb9c5a11086ee.1683541225.git.mazziesaccount@gmail.com/
> > > > [2]: https://elixir.bootlin.com/linux/v6.11/source/drivers/iio/industrialio-trigger.c#L732
> > > > [3]: https://elixir.bootlin.com/linux/v6.11/source/drivers/iio/industrialio-trigger.c#L752
> > >
> > > The signature of the two functions are different, the order of the
> > > parameters is switched. So you can't just swap them out for the
> > > `validate_trigger` callback since the signature is not compatible. But maybe
> > > you can update the implementation of one of the functions to calling the
> > > other function.
> > >
> >
> > Hi Lars,
> >
> > Hmm, I see what you mean. Still though, do you think that we could do some
> > cleaning here? I can see 3 approaches:
> >
> > 1) One of the 2 functions calls the other internally and nothing else has
> > to change.
>
> I would go with this. Changing the signatures to be the same would be (in
> my, not always humble enough, opinion) wrong. The different order of
> parameters reflects the different idea. One checks if device for trigger is
> the right one, the other checks if the trigger for the device is the right
> one. Thus, the order of parameters should be different.
>
> Calling the same implementation internally is fine with me. Maybe Jonathan
> will share his opinion when recovers from all the plumbing in Vienna ;)
>
> Yours,
> -- Matti
>
> --
> Matti Vaittinen
> Linux kernel developer at ROHM Semiconductors
> Oulu Finland
>
Hi Matti!
Thanks for your comment! Well, I still think in my eyes is better to
have one function do one thing instead of multiple. Also, I didn't
think of this argument with the order of arguments, it makes sense.
My experience is quite limited to how things should be in such a
large project so I trust your opinion. I would still like to see
what Jonathan has to say on this though, maybe he had some
reasoning behind!!!
Have a nice day!
Cheers,
Vasilis
next prev parent reply other threads:[~2024-09-22 11:07 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-21 18:19 [PATCH v1 0/2] iio: core: remove iio_validate_own_trigger() function Vasileios Amoiridis
2024-09-21 18:19 ` [PATCH v1 1/2] iio: Drop usage of iio_validate_own_trigger() Vasileios Amoiridis
2024-09-22 3:17 ` kernel test robot
2024-09-22 3:27 ` kernel test robot
2024-09-21 18:19 ` [PATCH v1 2/2] iio: remove iio_validate_own_trigger() completely Vasileios Amoiridis
2024-09-21 19:23 ` [PATCH v1 0/2] iio: core: remove iio_validate_own_trigger() function Lars-Peter Clausen
2024-09-21 20:07 ` Vasileios Amoiridis
2024-09-22 9:44 ` Matti Vaittinen
2024-09-22 11:07 ` Vasileios Amoiridis [this message]
2024-09-28 14:55 ` Jonathan Cameron
2024-09-29 10:36 ` Vasileios Amoiridis
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=20240922110721.GA439861@vamoiridPC \
--to=vassilisamir@gmail.com \
--cc=jic23@kernel.org \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mazziesaccount@gmail.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