mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: "Kangjie Lu" <kjlu@umn.edu>
Cc: <alsa-devel@alsa-project.org>, "Jaroslav Kysela" <perex@perex.cz>,
	<pakki001@umn.edu>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] sound: sb: fix a missing check of snd_ctl_add
Date: Tue, 01 Jan 2019 09:55:33 +0100	[thread overview]
Message-ID: <s5hpntgiwoq.wl-tiwai@suse.de> (raw)
In-Reply-To: <20181226014534.71083-1-kjlu@umn.edu>

On Wed, 26 Dec 2018 02:45:32 +0100,
Kangjie Lu wrote:
> 
> snd_ctl_add() could fail, so let's check its return value and return its
> error code upstream upon failure.
> 
> Signed-off-by: Kangjie Lu <kjlu@umn.edu>
> ---
>  sound/isa/sb/sb16_main.c | 10 ++++++++--
>  1 file changed, 8 insertions(+), 2 deletions(-)
> 
> diff --git a/sound/isa/sb/sb16_main.c b/sound/isa/sb/sb16_main.c
> index 37e6ce7b0b13..c9b25dc1f78e 100644
> --- a/sound/isa/sb/sb16_main.c
> +++ b/sound/isa/sb/sb16_main.c
> @@ -879,8 +879,14 @@ int snd_sb16dsp_pcm(struct snd_sb *chip, int device)
>  	snd_pcm_set_ops(pcm, SNDRV_PCM_STREAM_PLAYBACK, &snd_sb16_playback_ops);
>  	snd_pcm_set_ops(pcm, SNDRV_PCM_STREAM_CAPTURE, &snd_sb16_capture_ops);
>  
> -	if (chip->dma16 >= 0 && chip->dma8 != chip->dma16)
> -		snd_ctl_add(card, snd_ctl_new1(&snd_sb16_dma_control, chip));
> +	if (chip->dma16 >= 0 && chip->dma8 != chip->dma16) {
> +		err =
> +			snd_ctl_add(card,
> +					snd_ctl_new1(&snd_sb16_dma_control,
> +						chip));
> +		if (err < 0)
> +			return err;
> +	}
>  	else
>  		pcm->info_flags = SNDRV_PCM_INFO_HALF_DUPLEX;

The code change looks OK, but could you fix the indentation and avoid
unneeded line breaks, as well as the missing braces for else-block?

Also, we keep "ALSA:" prefix for the subject line (except for ASoC
ones).  Please align with it.


thanks,

Takashi

      reply	other threads:[~2019-01-01  8:55 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-26  1:45 Kangjie Lu
2019-01-01  8:55 ` 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=s5hpntgiwoq.wl-tiwai@suse.de \
    --to=tiwai@suse.de \
    --cc=alsa-devel@alsa-project.org \
    --cc=kjlu@umn.edu \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pakki001@umn.edu \
    --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®