From: Jonathan Cameron <jic23@kernel.org>
To: Javier Carrasco <javier.carrasco.cruz@gmail.com>
Cc: linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org,
Jonathan Cameron <Jonathan.Cameron@huawei.com>,
Paul Cercueil <paul@crapouillou.net>
Subject: Re: [PATCH RESEND] iio: move LIGHT_UVA and LIGHT_UVB to the end of iio_modifier
Date: Sun, 28 Jan 2024 13:41:35 +0000 [thread overview]
Message-ID: <20240128134057.075b23ae@jic23-huawei> (raw)
In-Reply-To: <20240127200208.185815-1-javier.carrasco.cruz@gmail.com>
On Sat, 27 Jan 2024 21:02:08 +0100
Javier Carrasco <javier.carrasco.cruz@gmail.com> wrote:
> The new modifiers should have added to the end of the enum, so they do
> not affect the existing entries.
>
> No modifiers were added since then, so they can be moved safely to the
> end of the list.
>
> Move IIO_MOD_LIGHT_UVA and IIO_MOD_LIGHT_UVB to the end of iio_modifier.
>
> Fixes: b89710bd215e ("iio: add modifiers for A and B ultraviolet light")
> Suggested-by: Paul Cercueil <paul@crapouillou.net>
> Signed-off-by: Javier Carrasco <javier.carrasco.cruz@gmail.com>
Thanks for the resend.
Applied to the fixes-togreg branch of iio.git
Jonathan
> ---
> include/uapi/linux/iio/types.h | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/include/uapi/linux/iio/types.h b/include/uapi/linux/iio/types.h
> index 5060963707b1..f2e0b2d50e6b 100644
> --- a/include/uapi/linux/iio/types.h
> +++ b/include/uapi/linux/iio/types.h
> @@ -91,8 +91,6 @@ enum iio_modifier {
> IIO_MOD_CO2,
> IIO_MOD_VOC,
> IIO_MOD_LIGHT_UV,
> - IIO_MOD_LIGHT_UVA,
> - IIO_MOD_LIGHT_UVB,
> IIO_MOD_LIGHT_DUV,
> IIO_MOD_PM1,
> IIO_MOD_PM2P5,
> @@ -107,6 +105,8 @@ enum iio_modifier {
> IIO_MOD_PITCH,
> IIO_MOD_YAW,
> IIO_MOD_ROLL,
> + IIO_MOD_LIGHT_UVA,
> + IIO_MOD_LIGHT_UVB,
> };
>
> enum iio_event_type {
prev parent reply other threads:[~2024-01-28 13:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-27 20:02 [PATCH RESEND] iio: move LIGHT_UVA and LIGHT_UVB to the end of iio_modifier Javier Carrasco
2024-01-28 13:41 ` Jonathan Cameron [this message]
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=20240128134057.075b23ae@jic23-huawei \
--to=jic23@kernel.org \
--cc=Jonathan.Cameron@huawei.com \
--cc=javier.carrasco.cruz@gmail.com \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=paul@crapouillou.net \
/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