From: Markus Elfring <Markus.Elfring@web.de>
To: Zhu Jun <zhujun2@cmss.chinamobile.com>,
linux-sound@vger.kernel.org, "Geoffrey D. Bennett" <g@b4.vu>,
Jaroslav Kysela <perex@perex.cz>, Takashi Iwai <tiwai@suse.com>
Cc: LKML <linux-kernel@vger.kernel.org>, Mark Brown <broonie@kernel.org>
Subject: Re: [PATCH v2?] ALSA: scarlett2: Add error check after retrieving PEQ filter values
Date: Wed, 9 Oct 2024 10:17:15 +0200 [thread overview]
Message-ID: <988de26b-9522-47bb-b80b-a56bc5923109@web.de> (raw)
In-Reply-To: <20241009073211.7266-1-zhujun2@cmss.chinamobile.com>
> Add error check after retrieving PEQ filter values in scarlett2_update_filter_values
> that ensure function returns error if PEQ filter value retrieval fails
* It is usually preferred to end such a sentence with a dot, isn't it?
* Would you like to add any tags (like “Fixes” and “Cc”) accordingly?
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/process/submitting-patches.rst?h=v6.12-rc2#n145
…
> ---
> sound/usb/mixer_scarlett2.c | 3 +++
Please take version information better into account.
See also:
* https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/process/submitting-patches.rst?h=v6.12-rc2#n321
* https://lore.kernel.org/all/?q=%22This+looks+like+a+new+version+of+a+previously+submitted+patch%22
…
> +++ b/sound/usb/mixer_scarlett2.c
> @@ -5614,6 +5614,9 @@ static int scarlett2_update_filter_values(struct usb_mixer_interface *mixer)
> SCARLETT2_BIQUAD_COEFFS,
> peq_flt_values);
>
> + if (err < 0)
> + return err;
> +
> for (i = 0, dst_idx = 0; i < info->dsp_input_count; i++) {
…
May a blank line be omitted before the return value check?
Regards,
Markus
next prev parent reply other threads:[~2024-10-09 8:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-09 7:32 [PATCH] ALSA: scarlett2: Add error check after retrieving PEQ filter values Zhu Jun
2024-10-09 8:17 ` Markus Elfring [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-10-09 9:23 [PATCH v2] " Zhu Jun
2024-10-09 9:52 ` Markus Elfring
2024-10-11 9:18 ` 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=988de26b-9522-47bb-b80b-a56bc5923109@web.de \
--to=markus.elfring@web.de \
--cc=broonie@kernel.org \
--cc=g@b4.vu \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=perex@perex.cz \
--cc=tiwai@suse.com \
--cc=zhujun2@cmss.chinamobile.com \
/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