All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nicolin Chen <b42378@freescale.com>
To: Timur Tabi <timur@tabi.org>
Cc: fabio.estevam@freescale.com, alsa-devel@alsa-project.org,
	Mark Brown <broonie@kernel.org>,
	linuxppc-dev@lists.ozlabs.org, shawn.guo@linaro.org
Subject: Re: [PATCH] ASoC: fsl: Disable SSI in trigger() if RE/TE are both cleared
Date: Fri, 12 Jul 2013 12:19:45 +0800	[thread overview]
Message-ID: <20130712041944.GA27906@MrMyself> (raw)
In-Reply-To: <51DF826C.40208@tabi.org>

On Thu, Jul 11, 2013 at 11:13:32PM -0500, Timur Tabi wrote:
> Have you tested it on PowerPC?

Not actually. But I think it won't break the work flow since
the SSI modules on two platform should be literally identical.

But if you still have concern with it, you can ask Mark to wait
and test it later. I'm okay with your decision.

Thanks,
Nicolin Chen

WARNING: multiple messages have this Message-ID (diff)
From: Nicolin Chen <b42378@freescale.com>
To: Timur Tabi <timur@tabi.org>
Cc: fabio.estevam@freescale.com, alsa-devel@alsa-project.org,
	Mark Brown <broonie@kernel.org>,
	linuxppc-dev@lists.ozlabs.org, shawn.guo@linaro.org
Subject: Re: [alsa-devel] [PATCH] ASoC: fsl: Disable SSI in trigger() if RE/TE are both cleared
Date: Fri, 12 Jul 2013 12:19:45 +0800	[thread overview]
Message-ID: <20130712041944.GA27906@MrMyself> (raw)
In-Reply-To: <51DF826C.40208@tabi.org>

On Thu, Jul 11, 2013 at 11:13:32PM -0500, Timur Tabi wrote:
> Have you tested it on PowerPC?

Not actually. But I think it won't break the work flow since
the SSI modules on two platform should be literally identical.

But if you still have concern with it, you can ask Mark to wait
and test it later. I'm okay with your decision.

Thanks,
Nicolin Chen

  reply	other threads:[~2013-07-12  4:24 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-10 10:43 [PATCH] ASoC: fsl: Disable SSI in trigger() if RE/TE are both cleared Nicolin Chen
2013-07-10 10:43 ` Nicolin Chen
2013-07-11 14:07 ` Shawn Guo
2013-07-11 16:54 ` Mark Brown
2013-07-11 16:54   ` Mark Brown
2013-07-11 17:14   ` timur
2013-07-12  3:57     ` Nicolin Chen
2013-07-12  3:57       ` [alsa-devel] " Nicolin Chen
2013-07-12  4:00       ` Timur Tabi
2013-07-12  4:00         ` [alsa-devel] " Timur Tabi
2013-07-12  4:09         ` Nicolin Chen
2013-07-12  4:09           ` [alsa-devel] " Nicolin Chen
2013-07-12  4:13           ` Timur Tabi
2013-07-12  4:13             ` [alsa-devel] " Timur Tabi
2013-07-12  4:19             ` Nicolin Chen [this message]
2013-07-12  4:19               ` Nicolin Chen
2013-07-12  8:43         ` Mark Brown
2013-07-12  8:43           ` Mark Brown
2013-07-12 12:11           ` Timur Tabi
2013-07-12 12:11             ` [alsa-devel] " Timur Tabi
2013-07-12 13:32             ` Shawn Guo
2013-07-12 13:32               ` [alsa-devel] " Shawn Guo
2013-07-12 14:23             ` Mark Brown
2013-07-12 14:23               ` [alsa-devel] " Mark Brown

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=20130712041944.GA27906@MrMyself \
    --to=b42378@freescale.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@kernel.org \
    --cc=fabio.estevam@freescale.com \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=shawn.guo@linaro.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 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.