From: PC Liao <pc.liao@mediatek.com>
To: Mark Brown <broonie@kernel.org>
Cc: "alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
srv_heupstream <srv_heupstream@mediatek.com>,
"tiwai@suse.de" <tiwai@suse.de>,
"s.hauer@pengutronix.de" <s.hauer@pengutronix.de>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"Koro Chen (陳思翰)" <koro.chen@mediatek.com>,
"linux-mediatek@lists.infradead.org"
<linux-mediatek@lists.infradead.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH v3] ASoC: mediatek: Add second I2S on mt8173-rt5650 machine driver
Date: Mon, 18 Apr 2016 20:59:57 +0800 [thread overview]
Message-ID: <1460984397.4462.4.camel@mtksdaap41> (raw)
In-Reply-To: <20160418120352.GZ3217@sirena.org.uk>
Hi Mark,
On Mon, 2016-04-18 at 20:03 +0800, Mark Brown wrote:
> On Mon, Apr 18, 2016 at 07:36:20PM +0800, PC Liao wrote:
>
> > Could you please give some comments or suggestions?
>
> I don't have these patches. If you're getting review comments from
> other people please address them, it's quite possible I saw them and
> agreed with them.
>
> Please don't send content free pings and please allow a reasonable time
> for review. People get busy, go on holiday, attend conferences and so
> on so unless there is some reason for urgency (like critical bug fixes)
> please allow at least a couple of weeks for review. Sending content
> free pings just adds to the mail volume (if they are seen at all) and if
> something has gone wrong you'll have to resend the patches anyway.
I am so sorry about that..........
I have sent v4.
Thanks for your review and help.
prev parent reply other threads:[~2016-04-18 13:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-07 7:35 [PATCH v3] ASoC: mediatek: Add second I2S on mt8173-rt5650 machine driver PC Liao
2016-04-07 9:50 ` Matthias Brugger
2016-04-07 10:03 ` PC Liao
2016-04-18 11:36 ` PC Liao
2016-04-18 12:03 ` Mark Brown
2016-04-18 12:59 ` PC Liao [this message]
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=1460984397.4462.4.camel@mtksdaap41 \
--to=pc.liao@mediatek.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=koro.chen@mediatek.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=s.hauer@pengutronix.de \
--cc=srv_heupstream@mediatek.com \
--cc=tiwai@suse.de \
/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;
as well as URLs for NNTP newsgroup(s).