From: Takashi Iwai <tiwai@suse.de>
To: Chen Ni <nichen@iscas.ac.cn>
Cc: david.rhodes@cirrus.com, rf@opensource.cirrus.com,
perex@perex.cz, tiwai@suse.com, linux-sound@vger.kernel.org,
patches@opensource.cirrus.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ALSA: hda: cs35l56: Remove unnecessary NULL check before release_firmware()
Date: Tue, 25 Mar 2025 11:55:11 +0100 [thread overview]
Message-ID: <87ldstcrcg.wl-tiwai@suse.de> (raw)
In-Reply-To: <20250325084639.801054-1-nichen@iscas.ac.cn>
On Tue, 25 Mar 2025 09:46:39 +0100,
Chen Ni wrote:
>
> release_firmware() checks for NULL pointers internally.
> Remove unneeded NULL check for fmw here.
>
> Signed-off-by: Chen Ni <nichen@iscas.ac.cn>
Thanks, applied now.
Takashi
prev parent reply other threads:[~2025-03-25 10:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-25 8:46 [PATCH] ALSA: hda: cs35l56: Remove unnecessary NULL check before release_firmware() Chen Ni
2025-03-25 10: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=87ldstcrcg.wl-tiwai@suse.de \
--to=tiwai@suse.de \
--cc=david.rhodes@cirrus.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=nichen@iscas.ac.cn \
--cc=patches@opensource.cirrus.com \
--cc=perex@perex.cz \
--cc=rf@opensource.cirrus.com \
--cc=tiwai@suse.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