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 00/17] ALSA: emu10k1 & emux: fixes related to wavetable playback
Date: Fri, 05 Apr 2024 12:29:25 +0200 [thread overview]
Message-ID: <87zfu8m7ay.wl-tiwai@suse.de> (raw)
In-Reply-To: <Zg/NfajQ3gdsmbUb@ugly>
On Fri, 05 Apr 2024 12:07:57 +0200,
Oswald Buddenhagen wrote:
>
> On Fri, Apr 05, 2024 at 11:20:32AM +0200, Takashi Iwai wrote:
> > On Thu, 04 Apr 2024 12:00:31 +0200,
> > Oswald Buddenhagen wrote:
> >>
> >> ---
> >> This patch series needs to be applied on top of the patch titled
> >> "Revert "ALSA: emu10k1: fix synthesizer sample playback position and
> >> caching"".
> >
> > The patch set isn't cleanly applicable even after the revert patch.
> > The patch 7 fails.
> >
> > Please rebase to the latest for-linus branch and resubmit.
> >
> this makes no sense; i'm getting a bit-identical patch after the rebase
> (which is unsurprising, as the file in question wasn't touched in
> years).
>
> are you sure you didn't corrupt the patch somehow (it happened before,
> cf. summary of c960b012ec47)? or maybe you have an unpublished
> conflicting commit?
>
> if there is an actual problem and you just named the wrong patch, then i
> suspect that it's just git-am being stupid - the rebases from 6.8 and
> later from your master from about a week ago went through smoothly.
No, I used b4 at this time, and such a failure shouldn't happen.
Try by yourself to apply the submitted patch mails with git-am on the
latest for-linus (or master) branch.
thanks,
Takashi
next prev parent reply other threads:[~2024-04-05 10:30 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-04 10:00 [PATCH v2 00/17] ALSA: emu10k1 & emux: fixes related to wavetable playback Oswald Buddenhagen
2024-04-04 10:00 ` [PATCH v2 01/17] ALSA: emux: fix /proc teardown at module unload Oswald Buddenhagen
2024-04-04 10:00 ` [PATCH v2 02/17] ALSA: emux: prune unused parameter from snd_soundfont_load_guspatch() Oswald Buddenhagen
2024-04-04 10:00 ` [PATCH v2 03/17] ALSA: emux: fix validation of snd_emux.num_ports Oswald Buddenhagen
2024-04-04 10:00 ` [PATCH v2 04/17] ALSA: emux: fix init of patch_info.truesize in load_data() Oswald Buddenhagen
2024-04-04 10:00 ` [PATCH v2 05/17] ALSA: emu10k1: prune vestiges of SNDRV_SFNT_SAMPLE_{BIDIR,REVERSE}_LOOP support Oswald Buddenhagen
2024-04-04 10:00 ` [PATCH v2 06/17] ALSA: emux: centralize & improve patch info validation Oswald Buddenhagen
2024-04-04 10:00 ` [PATCH v2 07/17] ALSA: emux: improve patch ioctl data validation Oswald Buddenhagen
2024-04-04 10:00 ` [PATCH v2 08/17] ALSA: emu10k1: move patch loader assertions into low-level functions Oswald Buddenhagen
2024-04-04 10:00 ` [PATCH v2 09/17] ALSA: emu10k1: fix sample signedness issues in wavetable loader Oswald Buddenhagen
2024-04-04 10:00 ` [PATCH v2 10/17] ALSA: emu10k1: fix playback of 8-bit wavetable samples Oswald Buddenhagen
2024-04-04 10:00 ` [PATCH v2 11/17] ALSA: emu10k1: merge conditions in patch loader Oswald Buddenhagen
2024-04-04 10:00 ` [PATCH v2 12/17] ALSA: emu10k1: fix wavetable offset recalculation Oswald Buddenhagen
2024-04-04 10:00 ` [PATCH v2 13/17] ALSA: emu10k1: de-duplicate size calculations for 16-bit samples Oswald Buddenhagen
2024-04-04 10:00 ` [PATCH v2 14/17] ALSA: emu10k1: improve cache behavior documentation Oswald Buddenhagen
2024-04-04 10:00 ` [PATCH v2 15/17] ALSA: emu10k1: fix wavetable playback position and caching, take 2 Oswald Buddenhagen
2024-04-04 10:00 ` [PATCH v2 16/17] ALSA: emu10k1: shrink blank space in front of wavetable samples Oswald Buddenhagen
2024-04-04 10:00 ` [PATCH v2 17/17] ALSA: emux: simplify snd_sf_list.callback handling Oswald Buddenhagen
2024-04-05 9:20 ` [PATCH v2 00/17] ALSA: emu10k1 & emux: fixes related to wavetable playback Takashi Iwai
2024-04-05 10:07 ` Oswald Buddenhagen
2024-04-05 10:29 ` Takashi Iwai [this message]
2024-04-05 18:38 ` Oswald Buddenhagen
2024-04-06 6:40 ` 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=87zfu8m7ay.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