From: Mark Brown <broonie@kernel.org>
To: John Hsu <KCHSU0@nuvoton.com>
Cc: "alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
Anatol Pomozov <anatol.pomozov@gmail.com>,
Ben Zhang <benzh@chromium.org>,
Liam Girdwood <lgirdwood@gmail.com>,
YHCHuang@nuvoton.com, CTLIN0@nuvoton.com,
Yong Zhi <yong.zhi@intel.com>
Subject: Re: [PATCH] ASoC: Extend FLL function
Date: Thu, 25 Feb 2016 10:55:19 +0900 [thread overview]
Message-ID: <20160225015519.GW18327@sirena.org.uk> (raw)
In-Reply-To: <56CE33D4.10009@nuvoton.com>
[-- Attachment #1.1: Type: text/plain, Size: 644 bytes --]
On Thu, Feb 25, 2016 at 06:51:00AM +0800, John Hsu wrote:
> Hi Mark,
> Could you help to review and merge this patch?
> Some patches later about nau8825 driver will patch base on it. Thank you
> very much.
Please don't top post, reply in line with needed context. This allows
readers to readily follow the flow of conversation and understand what
you are talking about and also helps ensure that everything in the
discussion is being addressed.
I don't have whatever this patch is (I suspect the fact that there were
concerns raised meant I expected a new version). Please do try to use
subject lines reflecting the style to the subsystem.
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
next prev parent reply other threads:[~2016-02-25 1:55 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-31 7:55 [PATCH] ASoC: Extend FLL function John Hsu
2015-12-31 9:14 ` Anatol Pomozov
2016-01-04 10:04 ` John Hsu
2016-02-24 22:51 ` John Hsu
2016-02-25 1:55 ` Mark Brown [this message]
2016-02-25 17:34 ` John Hsu
2016-02-26 1:34 ` Mark Brown
2016-02-26 16:16 ` John Hsu
-- strict thread matches above, loose matches on Subject: below --
2016-01-06 7:27 [PATCH] ASoC: extend " John Hsu
2016-01-07 1:26 ` Anatol Pomozov
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=20160225015519.GW18327@sirena.org.uk \
--to=broonie@kernel.org \
--cc=CTLIN0@nuvoton.com \
--cc=KCHSU0@nuvoton.com \
--cc=YHCHuang@nuvoton.com \
--cc=alsa-devel@alsa-project.org \
--cc=anatol.pomozov@gmail.com \
--cc=benzh@chromium.org \
--cc=lgirdwood@gmail.com \
--cc=yong.zhi@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox