From: Jonathan Cameron <jic23@kernel.org>
To: Antoniu Miclaus <antoniu.miclaus@analog.com>
Cc: <linux-iio@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
Jonathan Cameron <Jonathan.Cameron@huawei.com>
Subject: Re: [PATCH v2] iio: freq: admv1014: Fix warning about dubious x & !y and improve readability
Date: Sat, 14 May 2022 16:11:36 +0100 [thread overview]
Message-ID: <20220514161136.772fd848@jic23-huawei> (raw)
In-Reply-To: <20220511090006.90502-1-antoniu.miclaus@analog.com>
On Wed, 11 May 2022 12:00:06 +0300
Antoniu Miclaus <antoniu.miclaus@analog.com> wrote:
> The warning comes from __BF_FIELD_CHECK()
> specifically
>
> BUILD_BUG_ON_MSG(__builtin_constant_p(_val) ? \
> ~((_mask) >> __bf_shf(_mask)) & (_val) : 0, \
> _pfx "value too large for the field"); \
>
> The code was using !(enum value) which is not particularly easy to follow
> so replace that with explicit matching and use of ? 0 : 1; or ? 1 : 0;
> to improve readability.
>
> Signed-off-by: Jonathan Cameron <Jonathan.Cameron@huawei.com>
> Signed-off-by: Antoniu Miclaus <antoniu.miclaus@analog.com>
Thanks.
Applied tot he fixes-togreg branch of iio.git.
Thanks,
Jonathan
> ---
> changes in v2:
> - fix the logic for the input mode set bits
> drivers/iio/frequency/admv1014.c | 6 ++++--
> 1 file changed, 4 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/iio/frequency/admv1014.c b/drivers/iio/frequency/admv1014.c
> index a7994f8e6b9b..1aac5665b5de 100644
> --- a/drivers/iio/frequency/admv1014.c
> +++ b/drivers/iio/frequency/admv1014.c
> @@ -700,8 +700,10 @@ static int admv1014_init(struct admv1014_state *st)
> ADMV1014_DET_EN_MSK;
>
> enable_reg = FIELD_PREP(ADMV1014_P1DB_COMPENSATION_MSK, st->p1db_comp ? 3 : 0) |
> - FIELD_PREP(ADMV1014_IF_AMP_PD_MSK, !(st->input_mode)) |
> - FIELD_PREP(ADMV1014_BB_AMP_PD_MSK, st->input_mode) |
> + FIELD_PREP(ADMV1014_IF_AMP_PD_MSK,
> + (st->input_mode == ADMV1014_IF_MODE) ? 0 : 1) |
> + FIELD_PREP(ADMV1014_BB_AMP_PD_MSK,
> + (st->input_mode == ADMV1014_IF_MODE) ? 1 : 0) |
> FIELD_PREP(ADMV1014_DET_EN_MSK, st->det_en);
>
> return __admv1014_spi_update_bits(st, ADMV1014_REG_ENABLE, enable_reg_msk, enable_reg);
prev parent reply other threads:[~2022-05-14 15:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-11 9:00 [PATCH v2] iio: freq: admv1014: Fix warning about dubious x & !y and improve readability Antoniu Miclaus
2022-05-14 15:11 ` 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=20220514161136.772fd848@jic23-huawei \
--to=jic23@kernel.org \
--cc=Jonathan.Cameron@huawei.com \
--cc=antoniu.miclaus@analog.com \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox