From: Jerome Brunet <jbrunet@baylibre.com>
To: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>,
alsa-devel@alsa-project.org
Cc: tiwai@suse.de, broonie@kernel.org, Lee Jones <lee.jones@linaro.org>
Subject: Re: [PATCH 0/3] ASoC: Clean-up W=1 build warnings - part3
Date: Tue, 07 Jul 2020 21:39:58 +0200 [thread overview]
Message-ID: <1jo8ordshd.fsf@starbuckisacylon.baylibre.com> (raw)
In-Reply-To: <20200707192310.98663-1-pierre-louis.bossart@linux.intel.com>
On Tue 07 Jul 2020 at 21:23, Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com> wrote:
> This is a much smaller set of cleanups, all related to warnings thrown
> by the use of GENMASK() with an unsigned variable. I just made the
> warning go away but I wonder if there's a better fix in the definition
> of GENMASK() itself?
Looking at the patch I was going to ask the same thing.
It does not make much sense to me to force GENMASK arguments to be
integer (instead of unsigned integer) to then check there are positive ...
>
> Pierre-Louis Bossart (3):
> ASoC: Intel: Skylake: remove comparison always false warning
> ASoC: meson: axg-pdm: remove comparison always false warning
> ASoC: meson: axg-spdifin: remove comparison always false warning
>
> sound/soc/intel/skylake/skl-sst-dsp.c | 2 +-
> sound/soc/meson/axg-pdm.c | 2 +-
> sound/soc/meson/axg-spdifin.c | 2 +-
> 3 files changed, 3 insertions(+), 3 deletions(-)
next prev parent reply other threads:[~2020-07-07 19:41 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-07 19:23 [PATCH 0/3] ASoC: Clean-up W=1 build warnings - part3 Pierre-Louis Bossart
2020-07-07 19:23 ` [PATCH 1/3] ASoC: Intel: Skylake: remove comparison always false warning Pierre-Louis Bossart
2020-07-07 19:23 ` Pierre-Louis Bossart
2020-07-07 19:23 ` [PATCH 2/3] ASoC: meson: axg-pdm: " Pierre-Louis Bossart
2020-07-07 19:23 ` Pierre-Louis Bossart
2020-07-07 19:23 ` Pierre-Louis Bossart
2020-07-07 19:23 ` Pierre-Louis Bossart
2020-07-07 19:23 ` [PATCH 3/3] ASoC: meson: axg-spdifin: " Pierre-Louis Bossart
2020-07-07 19:23 ` Pierre-Louis Bossart
2020-07-07 19:23 ` Pierre-Louis Bossart
2020-07-07 19:23 ` Pierre-Louis Bossart
2020-07-07 19:39 ` Jerome Brunet [this message]
2020-07-08 0:16 ` [PATCH 0/3] ASoC: Clean-up W=1 build warnings - part3 Pierre-Louis Bossart
2020-07-08 6:31 ` Lee Jones
2020-07-08 11:13 ` Mark Brown
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=1jo8ordshd.fsf@starbuckisacylon.baylibre.com \
--to=jbrunet@baylibre.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=lee.jones@linaro.org \
--cc=pierre-louis.bossart@linux.intel.com \
--cc=tiwai@suse.de \
/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.