From: Mark Brown <broonie@kernel.org>
To: PC Liao <pc.liao@mediatek.com>
Cc: "tiwai@suse.de" <tiwai@suse.de>,
srv_heupstream <srv_heupstream@mediatek.com>,
"linux-mediatek@lists.infradead.org"
<linux-mediatek@lists.infradead.org>,
"s.hauer@pengutronix.de" <s.hauer@pengutronix.de>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
"Koro Chen (陳思翰)" <koro.chen@mediatek.com>
Subject: Re: [PATCH v3] ASoC: mediatek: Add second I2S on mt8173-rt5650 machine driver
Date: Mon, 18 Apr 2016 13:03:52 +0100 [thread overview]
Message-ID: <20160418120352.GZ3217@sirena.org.uk> (raw)
In-Reply-To: <1460979380.17045.2.camel@mtksdaap41>
[-- Attachment #1: Type: text/plain, Size: 709 bytes --]
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.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
next prev parent reply other threads:[~2016-04-18 12:03 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 [this message]
2016-04-18 12:59 ` PC Liao
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=20160418120352.GZ3217@sirena.org.uk \
--to=broonie@kernel.org \
--cc=alsa-devel@alsa-project.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=pc.liao@mediatek.com \
--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