From: "Nuno Sá" <noname.nuno@gmail.com>
To: Ramona Bolboaca <ramona.bolboaca@analog.com>,
jic23@kernel.org, nuno.sa@analog.com, linux-iio@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 1/3] iio: imu: adis16475.c: Remove unused enum elements
Date: Thu, 20 Jul 2023 09:38:50 +0200 [thread overview]
Message-ID: <e2fa1ebc820745065e91bac875f287167a0cfef9.camel@gmail.com> (raw)
In-Reply-To: <20230719123152.309624-2-ramona.bolboaca@analog.com>
On Wed, 2023-07-19 at 15:31 +0300, Ramona Bolboaca wrote:
> Remove unused enum elements ADIS16475_SCAN_DIAG_S_FLAGS and
> ADIS16475_SCAN_CRC_FAILURE.
>
> Signed-off-by: Ramona Bolboaca <ramona.bolboaca@analog.com>
> ---
Reviewed-by: Nuno Sa <nuno.sa@analog.com>
> drivers/iio/imu/adis16475.c | 2 --
> 1 file changed, 2 deletions(-)
>
> diff --git a/drivers/iio/imu/adis16475.c b/drivers/iio/imu/adis16475.c
> index 3abffb01ba31..243f0a91fdf9 100644
> --- a/drivers/iio/imu/adis16475.c
> +++ b/drivers/iio/imu/adis16475.c
> @@ -115,8 +115,6 @@ enum {
> ADIS16475_SCAN_ACCEL_Y,
> ADIS16475_SCAN_ACCEL_Z,
> ADIS16475_SCAN_TEMP,
> - ADIS16475_SCAN_DIAG_S_FLAGS,
> - ADIS16475_SCAN_CRC_FAILURE,
> };
>
> static bool low_rate_allow;
next prev parent reply other threads:[~2023-07-20 7:36 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-19 12:31 [PATCH v2 0/3] Add new channels for adis16475 Ramona Bolboaca
2023-07-19 12:31 ` [PATCH v2 1/3] iio: imu: adis16475.c: Remove unused enum elements Ramona Bolboaca
2023-07-20 7:38 ` Nuno Sá [this message]
2023-07-23 12:23 ` Jonathan Cameron
2023-07-19 12:31 ` [PATCH v2 2/3] iio: imu: adis16475.c: Add has_burst32 flag to adis16477 devices Ramona Bolboaca
2023-07-20 7:39 ` Nuno Sá
2023-07-23 12:24 ` Jonathan Cameron
2023-07-19 12:31 ` [PATCH v2 3/3] iio: imu: adis16475.c: Add delta angle and delta velocity channels Ramona Bolboaca
2023-07-20 8:58 ` Nuno Sá
2023-07-23 12:32 ` Jonathan Cameron
2023-07-23 12:36 ` Jonathan Cameron
2023-07-26 10:23 ` Bolboaca, Ramona
2023-07-29 14:47 ` 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=e2fa1ebc820745065e91bac875f287167a0cfef9.camel@gmail.com \
--to=noname.nuno@gmail.com \
--cc=jic23@kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nuno.sa@analog.com \
--cc=ramona.bolboaca@analog.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