[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20221203162008.007df587@jic23-huawei>
Date: Sat, 3 Dec 2022 16:20:08 +0000
From: Jonathan Cameron <jic23@...nel.org>
To: William Breathitt Gray <william.gray@...aro.org>
Cc: Fabrice Gasnier <fabrice.gasnier@...s.st.com>, lars@...afoo.de,
benjamin.gaignard@...com, mcoquelin.stm32@...il.com,
alexandre.torgue@...s.st.com, linux-iio@...r.kernel.org,
linux-stm32@...md-mailman.stormreply.com,
linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org
Subject: Re: Removing the last of IIO_COUNT (stm32-timer-trigger)
...
> > ---
> > To conclude, there some open items here, but hopefully nothing blocking.
> > In case we sort all these, this will allow to remove the IIO_COUNT
> > channel (along with the IIO device) being registered.
>
> I'm certain Jonathan will want some sort of deprecation schedule first
> to make sure any existing users have time to migrate to the Counter
> interface before we remove the IIO one, but it will give me a nice
> feeling of completion to see the last of IIO_COUNT superceded by the
> Counter interface. ;-)
If there is nothing in tree, I'm fine 'removing' it. However, note
that we'll have to keep a placeholder for some of the defines to avoid
renumbering other types etc. So probably just stick a couple of underscores
in front to make it __IIO_COUNT and add a comment to say it should not be used.
Jonathan
>
Powered by blists - more mailing lists