From: Mark Brown <broonie@kernel.org>
To: Bard Liao <bardliao@realtek.com>
Cc: Oder Chiou <oder_chiou@realtek.com>,
"alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
Lars-Peter Clausen <lars@metafoo.de>,
"mengdong.lin@intel.com" <mengdong.lin@intel.com>,
"lgirdwood@gmail.com" <lgirdwood@gmail.com>,
"yao.jin@intel.com" <yao.jin@intel.com>,
Flove <flove@realtek.com>
Subject: Re: [PATCH 2/4] ASoC: rt5670: check if asrc is useable
Date: Fri, 14 Nov 2014 15:11:25 +0000 [thread overview]
Message-ID: <20141114151125.GD3815@sirena.org.uk> (raw)
In-Reply-To: <ABFD875FF5FB574BA706497D987D48D701021F56@RTITMBSV03.realtek.com.tw>
[-- Attachment #1.1: Type: text/plain, Size: 366 bytes --]
On Fri, Nov 14, 2014 at 11:38:51AM +0000, Bard Liao wrote:
> Sure, I will resend the patch. Another question is that the patch is one
> of 4 patches series. Should I resend all of them?
No need to send patch 1 since I applied it but please resend the rest -
I assumed that patches 3 and 4 depended on patch 2. In general resend
anything that hasn't been applied.
[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
next prev parent reply other threads:[~2014-11-14 15:12 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-12 11:54 [PATCH 1/4] ASoC: rt5670: make bias level more reasonable bardliao
2014-11-12 11:54 ` [PATCH 2/4] ASoC: rt5670: check if asrc is useable bardliao
2014-11-12 19:42 ` Lars-Peter Clausen
2014-11-14 11:38 ` Bard Liao
2014-11-14 15:11 ` Mark Brown [this message]
2014-11-12 11:54 ` [PATCH 3/4] ASoC: rt5670: add DMIC ASRC support bardliao
2014-11-12 11:54 ` [PATCH 4/4] ASoC: rt5670: add codec irq support bardliao
2014-11-14 11:11 ` [PATCH 1/4] ASoC: rt5670: make bias level more reasonable Mark Brown
-- strict thread matches above, loose matches on Subject: below --
2014-11-12 6:21 bardliao
2014-11-12 6:21 ` [PATCH 2/4] ASoC: rt5670: check if asrc is useable bardliao
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=20141114151125.GD3815@sirena.org.uk \
--to=broonie@kernel.org \
--cc=alsa-devel@alsa-project.org \
--cc=bardliao@realtek.com \
--cc=flove@realtek.com \
--cc=lars@metafoo.de \
--cc=lgirdwood@gmail.com \
--cc=mengdong.lin@intel.com \
--cc=oder_chiou@realtek.com \
--cc=yao.jin@intel.com \
/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.