[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <s5htup4exbl.wl-tiwai@suse.de>
Date: Sun, 21 Mar 2021 09:16:14 +0100
From: Takashi Iwai <tiwai@...e.de>
To: Tong Zhang <ztong0001@...il.com>
Cc: Jaroslav Kysela <perex@...ex.cz>, Takashi Iwai <tiwai@...e.com>,
Romain Perier <romain.perier@...il.com>,
Allen Pais <allen.lkml@...il.com>,
Leon Romanovsky <leon@...nel.org>,
Jasmin Fazlic <superfassl@...il.com>,
Mark Brown <broonie@...nel.org>, Joe Perches <joe@...ches.com>,
Tom Rix <trix@...hat.com>,
Pierre-Louis Bossart <pierre-louis.bossart@...ux.intel.com>,
"Gustavo A. R. Silva" <gustavoars@...nel.org>,
alsa-devel@...a-project.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2 0/3] ALSA: hdsp and hdspm, don't disable device if not enabled
On Sat, 20 Mar 2021 23:23:33 +0100,
Tong Zhang wrote:
>
> This series fixes issues in hdsp and hdspm. The drivers in question want
> to disable a device that is not enabled on error path.
>
> v2: add fix to rme9652
>
> Tong Zhang (3):
> ALSA: hdsp: don't disable if not enabled
> ALSA: hdspm: don't disable if not enabled
> ALSA: rme9652: don't disable if not enabled
Thanks for the patches.
IMO, a safer way for this is to add pci_is_enabled() check in *_free()
functions around the call of pci_disable_device(). The point is that
*_free() is the sole destructor function that manages all stuff, hence
it's better to do all there. And, of course, it'll be less changes.
Care to resend v3 patches with that?
thanks,
Takashi
Powered by blists - more mailing lists