From: Takashi Iwai <tiwai@suse.de>
To: Oswald Buddenhagen <oswald.buddenhagen@gmx.de>
Cc: alsa-devel@alsa-project.org, Jaroslav Kysela <perex@perex.cz>
Subject: Re: [PATCH v2 9/9] ALSA: emu10k1: fix PCM playback buffer size constraints
Date: Thu, 18 May 2023 13:04:22 +0200 [thread overview]
Message-ID: <87mt21zyrt.wl-tiwai@suse.de> (raw)
In-Reply-To: <ZGXv3O1aCuDTrVz3@ugly>
On Thu, 18 May 2023 11:29:00 +0200,
Oswald Buddenhagen wrote:
>
> sorry for the "flood", i forgot to adjust the declaration of the
> series in my tool. you can ignore the other patches; they didn't
> change from what you already applied.
Don't worry, now I applied this one.
Thanks!
Takashi
prev parent reply other threads:[~2023-05-18 11:05 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-18 9:22 [PATCH v2 1/9] ALSA: emu10k1: pass frame instead of byte addresses Oswald Buddenhagen
2023-05-18 9:22 ` [PATCH v2 2/9] Revert "ALSA: emu10k1 - delay the PCM interrupts (add pcm_irq_delay parameter)" Oswald Buddenhagen
2023-05-18 9:22 ` [PATCH v2 3/9] ALSA: emu10k1: remove pointless displacement of the extra voices Oswald Buddenhagen
2023-05-18 9:22 ` [PATCH v2 4/9] ALSA: emu10k1: skip pointless cache setup for " Oswald Buddenhagen
2023-05-18 9:22 ` [PATCH v2 5/9] ALSA: emu10k1: fix PCM playback cache and interrupt handling Oswald Buddenhagen
2023-05-18 9:22 ` [PATCH v2 6/9] ALSA: emu10k1: improve API of low-level voice manipulation functions Oswald Buddenhagen
2023-05-18 9:22 ` [PATCH v2 7/9] ALSA: emu10k1: refactor PCM playback cache filling Oswald Buddenhagen
2023-05-18 9:22 ` [PATCH v2 8/9] ALSA: emu10k1: refactor PCM playback address handling Oswald Buddenhagen
2023-05-18 9:22 ` [PATCH v2 9/9] ALSA: emu10k1: fix PCM playback buffer size constraints Oswald Buddenhagen
2023-05-18 9:29 ` Oswald Buddenhagen
2023-05-18 11:04 ` 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=87mt21zyrt.wl-tiwai@suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@alsa-project.org \
--cc=oswald.buddenhagen@gmx.de \
--cc=perex@perex.cz \
/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