[alsa-devel] [PATCHES_v1] ASoC: Towards dropping runtime field from snd_soc_dai

Mark Brown broonie at opensource.wolfsonmicro.com
Mon Feb 22 15:27:49 CET 2010

On Mon, Feb 22, 2010 at 03:55:59PM +0900, jassi brar wrote:

I've applied all three changes for 2.6.35 after testing on an AT91 board
here, thanks.  Unfortunately it looks like the SSC suspend and resume
code is a bit broken anyway since it doesn't seem to cope too well with
being suspended during playback but your patches don't affect that one
way or another.

> <Due to some problem I am unable to send inline patches, please accept
> the attached patches for this time>

If you're going to do this please send just the patches as the
attachments, including the patch description in the attachment cases
them to come out like this:

    ASOC: ATMEL: Getting cpu_dai method change
    [PATCH 2/3] ASOC: ATMEL: Getting cpu_dai method change
    Currently only the atmel driver make use of snd_soc_dai.runtime field.

when applied which isn't ideal.  It also seems that your attachments are
coming out base64 encoded rather than text/plain.

> [PATCH 1/3] ASoC: PLATFORM: Pass dai_link as argument to suspend, resume
> [PATCH 2/3] ASOC: ATMEL: Getting cpu_dai method change
> [PATCH 3/3] ASOC: SND_SOC_DAI: Get rid of 'runtime' field

Note also the different spellings of ASoC here (and elsewhere in your
commit messages) - the first is correct.  You don't need to capitalise
all the letters in names.

If your problems are (as I'm guessing is the case) gmail breakage you
might want to look into imap-send, which will dump the patches in an
IMAP mailbox for transmission.

More information about the Alsa-devel mailing list