From: Takashi Iwai <tiwai@suse.de>
To: "Jason A. Donenfeld" <Jason@zx2c4.com>
Cc: Takashi Iwai <tiwai@suse.com>, Al Viro <viro@zeniv.linux.org.uk>,
alsa-devel@alsa-project.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ALSA: au88x0: use explicitly signed char
Date: Tue, 25 Oct 2022 08:21:10 +0200 [thread overview]
Message-ID: <87czags9t5.wl-tiwai@suse.de> (raw)
In-Reply-To: <CAHmME9q2JOGMKNrXqK7q=xfZdciy89P+GT0eGHVmVqOvKDYA8g@mail.gmail.com>
On Tue, 25 Oct 2022 01:59:50 +0200,
Jason A. Donenfeld wrote:
>
> Hi Al,
>
> On Mon, Oct 24, 2022 at 11:11 PM Al Viro <viro@zeniv.linux.org.uk> wrote:
> >
> > On Mon, Oct 24, 2022 at 06:29:29PM +0200, Jason A. Donenfeld wrote:
> > > With char becoming unsigned by default, and with `char` alone being
> > > ambiguous and based on architecture, signed chars need to be marked
> > > explicitly as such. This fixes warnings like:
> >
> > It might make sparse to STFU, but it does *not* resolve the underlying
> > issue:
> >
> > vortex_adb_checkinout() returns a number in range of 0..31 on success
> > and -ENOMEM on failure. Quite a few callers don't bother to check...
>
> Yea, I saw that. I assume that the places that don't check don't
> *need* to check. But maybe this driver is junk and other bugs lurk.
> I'm not sure. Either way, I think this change is certainly an
> improvement on the status quo. I don't intend to develop further on
> it, but feel free to send patches atop once this lands.
Yes, the driver is likely broken in some other way, too.
Such a corner case doesn't hit usually, and it's unlikely worth to
spend too much time on it.
In anyway, I applied the patch now to for-next branch.
Thanks!
Takashi
prev parent reply other threads:[~2022-10-25 6:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-24 16:29 [PATCH] ALSA: au88x0: use explicitly signed char Jason A. Donenfeld
2022-10-24 21:11 ` Al Viro
2022-10-24 23:59 ` Jason A. Donenfeld
2022-10-25 6:21 ` Takashi Iwai [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=87czags9t5.wl-tiwai@suse.de \
--to=tiwai@suse.de \
--cc=Jason@zx2c4.com \
--cc=alsa-devel@alsa-project.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tiwai@suse.com \
--cc=viro@zeniv.linux.org.uk \
/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