From: Takashi Iwai <tiwai@suse.de>
To: Oswald Buddenhagen <oswald.buddenhagen@gmx.de>
Cc: alsa-devel@alsa-project.org
Subject: Re: [PATCH 0/6] ALSA: emu10k1: Various improvements related to locking
Date: Mon, 08 May 2023 09:33:47 +0200 [thread overview]
Message-ID: <871qjrffac.wl-tiwai@suse.de> (raw)
In-Reply-To: <20230428095941.1706278-1-oswald.buddenhagen@gmx.de>
On Fri, 28 Apr 2023 11:59:35 +0200,
Oswald Buddenhagen wrote:
>
> ---
>
> This patch series needs to be applied on top of the patch titled "ALSA:
> emu10k1: use more existing defines instead of open-coded numbers".
>
> Oswald Buddenhagen (6):
> ALSA: emu10k1: remove pointless locks from timer code
> ALSA: emu10k1: remove pointless locks from /proc code
> ALSA: emu10k1: use the right lock in snd_emu10k1_shared_spdif_put()
> ALSA: emu10k1: fix locking in snd_emu1010_fpga_link_dst_src_write()
> ALSA: core: update comment on snd_card.controls_rwsem
> ALSA: emu10k1: remove now superfluous mixer locking
Applied all six patches now.
thanks,
Takashi
prev parent reply other threads:[~2023-05-08 7:35 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-28 9:59 [PATCH 0/6] ALSA: emu10k1: Various improvements related to locking Oswald Buddenhagen
2023-04-28 9:59 ` [PATCH 1/6] ALSA: emu10k1: remove pointless locks from timer code Oswald Buddenhagen
2023-04-28 9:59 ` [PATCH 2/6] ALSA: emu10k1: remove pointless locks from /proc code Oswald Buddenhagen
2023-04-28 9:59 ` [PATCH 3/6] ALSA: emu10k1: use the right lock in snd_emu10k1_shared_spdif_put() Oswald Buddenhagen
2023-04-28 9:59 ` [PATCH 4/6] ALSA: emu10k1: fix locking in snd_emu1010_fpga_link_dst_src_write() Oswald Buddenhagen
2023-04-28 9:59 ` [PATCH 5/6] ALSA: core: update comment on snd_card.controls_rwsem Oswald Buddenhagen
2023-04-28 9:59 ` [PATCH 6/6] ALSA: emu10k1: remove now superfluous mixer locking Oswald Buddenhagen
2023-05-08 7:33 ` 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=871qjrffac.wl-tiwai@suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@alsa-project.org \
--cc=oswald.buddenhagen@gmx.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