From: Jonathan Cameron <jic23@kernel.org>
To: William Breathitt Gray <william.gray@linaro.org>
Cc: Fabrice Gasnier <fabrice.gasnier@foss.st.com>,
lars@metafoo.de, benjamin.gaignard@st.com,
mcoquelin.stm32@gmail.com, alexandre.torgue@foss.st.com,
linux-iio@vger.kernel.org,
linux-stm32@st-md-mailman.stormreply.com,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: Removing the last of IIO_COUNT (stm32-timer-trigger)
Date: Sat, 3 Dec 2022 16:20:08 +0000 [thread overview]
Message-ID: <20221203162008.007df587@jic23-huawei> (raw)
In-Reply-To: <Y4KuBicVeRAsfqxq@fedora>
...
> > ---
> > 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
>
WARNING: multiple messages have this Message-ID (diff)
From: Jonathan Cameron <jic23@kernel.org>
To: William Breathitt Gray <william.gray@linaro.org>
Cc: Fabrice Gasnier <fabrice.gasnier@foss.st.com>,
lars@metafoo.de, benjamin.gaignard@st.com,
mcoquelin.stm32@gmail.com, alexandre.torgue@foss.st.com,
linux-iio@vger.kernel.org,
linux-stm32@st-md-mailman.stormreply.com,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: Removing the last of IIO_COUNT (stm32-timer-trigger)
Date: Sat, 3 Dec 2022 16:20:08 +0000 [thread overview]
Message-ID: <20221203162008.007df587@jic23-huawei> (raw)
In-Reply-To: <Y4KuBicVeRAsfqxq@fedora>
...
> > ---
> > 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
>
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2022-12-03 16:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-16 12:05 Removing the last of IIO_COUNT (stm32-timer-trigger) William Breathitt Gray
2022-10-16 12:05 ` William Breathitt Gray
2022-10-27 9:41 ` Fabrice Gasnier
2022-10-27 9:41 ` Fabrice Gasnier
2022-11-27 0:23 ` William Breathitt Gray
2022-11-27 0:23 ` William Breathitt Gray
2022-12-03 16:20 ` Jonathan Cameron [this message]
2022-12-03 16:20 ` 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=20221203162008.007df587@jic23-huawei \
--to=jic23@kernel.org \
--cc=alexandre.torgue@foss.st.com \
--cc=benjamin.gaignard@st.com \
--cc=fabrice.gasnier@foss.st.com \
--cc=lars@metafoo.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=mcoquelin.stm32@gmail.com \
--cc=william.gray@linaro.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.