From: Oswald Buddenhagen <oswald.buddenhagen@gmx.de>
To: alsa-devel@alsa-project.org
Subject: Re: [PATCH 1/7] ALSA: emu10k1: drop redundant snd_emu10k1_efx_playback_hw_free()
Date: Fri, 21 Apr 2023 17:16:04 +0200 [thread overview]
Message-ID: <ZEKotHwG1CjoSDek@ugly> (raw)
In-Reply-To: <87r0sdqo5n.wl-tiwai@suse.de>
On Fri, Apr 21, 2023 at 04:56:52PM +0200, Takashi Iwai wrote:
>Also, when you submit this size of patch series, please make a cover
>letter and explain what the series are intended.
>
i've actually pondered that and concluded that it would be kinda
pointless, because the theme "cleanups" is rather obvious.
for the other series it would be "fpga access fixes & cleanups", which
also seemed obvious enough.
anyway, i'll lower the "threshold of noteworthiness" for the future.
regards
next prev parent reply other threads:[~2023-04-21 15:17 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-21 14:10 [PATCH 1/7] ALSA: emu10k1: drop redundant snd_emu10k1_efx_playback_hw_free() Oswald Buddenhagen
2023-04-21 14:10 ` [PATCH 2/7] ALSA: emu10k1: drop redundant snd_emu10k1_efx_playback_pointer() Oswald Buddenhagen
2023-04-21 14:10 ` [PATCH 3/7] ALSA: emu10k1: remove obsolete card type variable and defines Oswald Buddenhagen
2023-04-21 14:10 ` [PATCH 4/7] ALSA: emu10k1: remove unused `resume` parameter from snd_emu10k1_init() Oswald Buddenhagen
2023-04-21 14:54 ` Takashi Iwai
2023-04-21 14:10 ` [PATCH 5/7] ALSA: emu10k1: remove unused snd_emu10k1_voice.emu field Oswald Buddenhagen
2023-04-21 14:10 ` [PATCH 6/7] ALSA: emu10k1: remove unused emu->pcm_playback_efx_substream field Oswald Buddenhagen
2023-04-21 14:54 ` Takashi Iwai
2023-04-21 15:00 ` Oswald Buddenhagen
2023-04-21 14:10 ` [PATCH 7/7] ALSA: emu10k1: clean up P16V part somewhat Oswald Buddenhagen
2023-04-21 14:56 ` [PATCH 1/7] ALSA: emu10k1: drop redundant snd_emu10k1_efx_playback_hw_free() Takashi Iwai
2023-04-21 15:16 ` Oswald Buddenhagen [this message]
2023-04-22 8:44 ` 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=ZEKotHwG1CjoSDek@ugly \
--to=oswald.buddenhagen@gmx.de \
--cc=alsa-devel@alsa-project.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.