public inbox for alsa-devel@alsa-project.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Oswald Buddenhagen <oswald.buddenhagen@gmx.de>
Cc: alsa-devel@alsa-project.org
Subject: Re: [PATCH] ALSA: emu10k1: fix error codes
Date: Sat, 22 Apr 2023 09:46:24 +0200	[thread overview]
Message-ID: <87y1mkpdf3.wl-tiwai@suse.de> (raw)
In-Reply-To: <20230421172623.1017222-1-oswald.buddenhagen@gmx.de>

On Fri, 21 Apr 2023 19:26:23 +0200,
Oswald Buddenhagen wrote:
> 
> One might argue that this potentially breaks user space, but a) this is
> just one driver among many, so it seems unlikely that someone would
> expect (only) the broken codes and b) it seems unlikely that someone
> would check these syscalls for particular errors at all, rather than
> just logging them (this might be debatable for the voice allocator
> calls).
> 
> Signed-off-by: Oswald Buddenhagen <oswald.buddenhagen@gmx.de>

I find this is too risky for really little win.  The error code is
returned to user space in quite many cases; e.g. the voice allocator
is called from PCM hw_params, too, and that's most of user-space
programs do actually check.  It could be a surprise if it's changed
without much reason, may trigger unexpected behavior changes.

Of course, if the error code must be corrected, we can fix it.
But I don't see it in this patch description.


thanks,

Takashi

  reply	other threads:[~2023-04-22  7:47 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-21 17:26 [PATCH] ALSA: emu10k1: fix error codes Oswald Buddenhagen
2023-04-22  7:46 ` Takashi Iwai [this message]
2023-04-22 12:04   ` Oswald Buddenhagen
2023-04-22 15:31     ` Takashi Iwai

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=87y1mkpdf3.wl-tiwai@suse.de \
    --to=tiwai@suse.de \
    --cc=alsa-devel@alsa-project.org \
    --cc=oswald.buddenhagen@gmx.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox