Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: Nicolin Chen <Guangyu.Chen@freescale.com>
Cc: linux-kernel@vger.kernel.org, linuxppc-dev@lists.ozlabs.org,
	alsa-devel@alsa-project.org, timur@tabi.org,
	Li.Xiubo@freescale.com
Subject: Re: [PATCH bisect 0/2] ASoC: fsl_sai: Overwrite trigger()
Date: Tue, 1 Apr 2014 12:04:12 +0100	[thread overview]
Message-ID: <20140401110412.GJ2269@sirena.org.uk> (raw)
In-Reply-To: <1396322227-482-1-git-send-email-Guangyu.Chen@freescale.com>

[-- Attachment #1: Type: text/plain, Size: 234 bytes --]

On Tue, Apr 01, 2014 at 11:17:05AM +0800, Nicolin Chen wrote:

> * The patches are generated by using '-U2' because the default '-U3'
>   would conflict the baseline without fsl_sai_isr patches.

What are these "fsi_sai_isr patches"?

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

  parent reply	other threads:[~2014-04-01 11:04 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-01  3:17 [PATCH bisect 0/2] ASoC: fsl_sai: Overwrite trigger() Nicolin Chen
2014-04-01  3:17 ` [PATCH bisect 1/2] ASoC: fsl_sai: Fix buggy configurations in trigger() Nicolin Chen
2014-04-01 11:56   ` Mark Brown
2014-04-01  3:17 ` [PATCH bisect 2/2] ASoC: fsl_sai: Separately enable interrupts for Tx and Rx streams Nicolin Chen
2014-04-01  3:25   ` Dongsheng.Wang
2014-04-01  3:14     ` Nicolin Chen
2014-04-01  3:48       ` Dongsheng.Wang
2014-04-01  3:37         ` Nicolin Chen
2014-04-01  4:19           ` Dongsheng.Wang
2014-04-01 12:07   ` Mark Brown
2014-04-01 13:21     ` Nicolin Chen
2014-04-01 16:42       ` Mark Brown
2014-04-02  2:18         ` Nicolin Chen
2014-04-01 11:04 ` Mark Brown [this message]
2014-04-01 10:54   ` [PATCH bisect 0/2] ASoC: fsl_sai: Overwrite trigger() Nicolin Chen

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=20140401110412.GJ2269@sirena.org.uk \
    --to=broonie@kernel.org \
    --cc=Guangyu.Chen@freescale.com \
    --cc=Li.Xiubo@freescale.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=timur@tabi.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox