From: Takashi Iwai <tiwai@suse.de>
To: Matthias Kaehlcke <mka@chromium.org>
Cc: Jaroslav Kysela <perex@perex.cz>, Sven Hahne <hahne@zeitkunst.eu>,
Julia Lawall <Julia.Lawall@lip6.fr>,
alsa-devel@alsa-project.org,
Grant Grundler <grundler@chromium.org>,
linux-kernel@vger.kernel.org,
Greg Hackmann <ghackmann@google.com>,
Michael Davidson <md@google.com>
Subject: Re: [alsa-devel] [PATCH] ALSA: hda/ca0132: Limit values for chip addresses to 32-bit
Date: Mon, 20 Mar 2017 10:33:43 +0100 [thread overview]
Message-ID: <s5hy3w0wavc.wl-tiwai@suse.de> (raw)
In-Reply-To: <20170316205223.16926-1-mka@chromium.org>
On Thu, 16 Mar 2017 21:52:23 +0100,
Matthias Kaehlcke wrote:
>
> With the previous unsigned long value clang generates warnings like
> this:
>
> sound/pci/hda/patch_ca0132.c:860:37: error: implicit conversion from
> 'unsigned long' to 'u32' (aka 'unsigned int') changes value from
> 18446744073709551615 to 4294967295 [-Werror,-Wconstant-conversion]
> spec->curr_chip_addx = (res < 0) ? ~0UL : chip_addx;
> ~ ^~~~
>
> Signed-off-by: Matthias Kaehlcke <mka@chromium.org>
Thanks for the patch. The changes look mostly OK, but...
> ---
> sound/pci/hda/patch_ca0132.c | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/sound/pci/hda/patch_ca0132.c b/sound/pci/hda/patch_ca0132.c
> index 11b9b2f17a2e..7175e2b46fc4 100644
> --- a/sound/pci/hda/patch_ca0132.c
> +++ b/sound/pci/hda/patch_ca0132.c
> @@ -857,7 +857,7 @@ static int chipio_write_address(struct hda_codec *codec,
> chip_addx >> 16);
> }
>
> - spec->curr_chip_addx = (res < 0) ? ~0UL : chip_addx;
> + spec->curr_chip_addx = (res < 0) ? (u32)~0U : chip_addx;
... I guess the cast to u32 is superfluous here? That is, just
replace UL to U should work, I suppose. (Ditto for all other places.)
Takashi
next prev parent reply other threads:[~2017-03-20 9:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-16 20:52 Matthias Kaehlcke
2017-03-20 9:33 ` Takashi Iwai [this message]
2017-04-01 0:52 ` [alsa-devel] " Matthias Kaehlcke
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=s5hy3w0wavc.wl-tiwai@suse.de \
--to=tiwai@suse.de \
--cc=Julia.Lawall@lip6.fr \
--cc=alsa-devel@alsa-project.org \
--cc=ghackmann@google.com \
--cc=grundler@chromium.org \
--cc=hahne@zeitkunst.eu \
--cc=linux-kernel@vger.kernel.org \
--cc=md@google.com \
--cc=mka@chromium.org \
--cc=perex@perex.cz \
/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
all inboxes | Powered by JetHome®