From: Takashi Sakamoto <o-takashi@sakamocchi.jp>
To: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
Cc: Jaroslav Kysela <perex@perex.cz>, Takashi Iwai <tiwai@suse.com>,
Thierry Reding <thierry.reding@gmail.com>,
Jonathan Hunter <jonathanh@nvidia.com>,
Geoff Levand <geoff@infradead.org>,
Michael Ellerman <mpe@ellerman.id.au>,
alsa-devel@alsa-project.org, kernel@pengutronix.de,
Nicholas Piggin <npiggin@gmail.com>,
Christophe Leroy <christophe.leroy@csgroup.eu>,
linux-tegra@vger.kernel.org, linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH 0/3] ALSA: core: Make some functions return void
Date: Wed, 8 Feb 2023 17:33:48 +0900 [thread overview]
Message-ID: <Y+NebPBazKrqJoEZ@workstation> (raw)
In-Reply-To: <20230207191907.467756-1-u.kleine-koenig@pengutronix.de>
Hi,
On Tue, Feb 07, 2023 at 08:19:04PM +0100, Uwe Kleine-König wrote:
> Hello,
>
> while checking in which cases hda_tegra_remove() can return a non-zero value, I
> found that actually cannot happen. This series makes the involved functions
> return void to make this obvious.
>
> This is a preparation for making platform_driver::remove return void, too.
>
> Best regards
> Uwe
>
> Uwe Kleine-König (3):
> ALSA: core: Make snd_card_disconnect() return void
> ALSA: core: Make snd_card_free_when_closed() return void
> ALSA: core: Make snd_card_free() return void
>
> include/sound/core.h | 6 +++---
> sound/core/init.c | 40 ++++++++++++++-------------------------
> sound/pci/hda/hda_tegra.c | 6 ++----
> sound/ppc/snd_ps3.c | 4 +---
> 4 files changed, 20 insertions(+), 36 deletions(-)
All of the changes in the patches look good to me, as the return value
seems not to be so effective for a long time (15 years or more) and
expected so for future.
Reviewed-by: Takashi Sakamoto <o-takashi@sakamocchi.jp>
One of my concern is that we are mostly in the last week for v6.3
development. When taking influence of the changes into account, it
would be possible to postpone to v6.4 development. But it's up to the
maintainer.
> base-commit: 05ecb680708a1dbe6554d6fc17e5d9a8a7cb5e6a
A small nitpicking. I think you use Linus' tree or so:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=05ecb680708a
Because the hash is not reachable from the branch for next merge window on
the tree of sound subsystem upstream:
https://git.kernel.org/pub/scm/linux/kernel/git/tiwai/sound.git/commit/?h=for-next&id=05ecb680708a
I guess it is safer to use his tree as your work-base, even
if the three patches can be applied to it as is (fortunately).
Regards
Takashi Sakamoto
next prev parent reply other threads:[~2023-02-08 8:33 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-07 19:19 [PATCH 0/3] ALSA: core: Make some functions return void Uwe Kleine-König
2023-02-07 19:19 ` [PATCH 3/3] ALSA: core: Make snd_card_free() " Uwe Kleine-König
2023-02-08 2:10 ` Geoff Levand
2023-02-08 11:33 ` Thierry Reding
2023-02-08 8:33 ` Takashi Sakamoto [this message]
2023-02-08 9:25 ` [PATCH 0/3] ALSA: core: Make some functions " Uwe Kleine-König
2023-02-08 8:39 ` Jaroslav Kysela
2023-02-08 12:41 ` 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=Y+NebPBazKrqJoEZ@workstation \
--to=o-takashi@sakamocchi.jp \
--cc=alsa-devel@alsa-project.org \
--cc=christophe.leroy@csgroup.eu \
--cc=geoff@infradead.org \
--cc=jonathanh@nvidia.com \
--cc=kernel@pengutronix.de \
--cc=linux-tegra@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.au \
--cc=npiggin@gmail.com \
--cc=perex@perex.cz \
--cc=thierry.reding@gmail.com \
--cc=tiwai@suse.com \
--cc=u.kleine-koenig@pengutronix.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