From: Han Lu <han.lu@linux.intel.com>
To: Mark Brown <broonie@kernel.org>, Takashi Iwai <tiwai@suse.de>
Cc: vinod.koul@intel.com, han.lu@intel.com,
alsa-devel@alsa-project.org,
pierre-louis.bossart@linux.intel.com,
liam.r.girdwood@linux.intel.com
Subject: Re: [PATCH V7 0/2] ASoC: Add core API to register and cleanup DMI names for card
Date: Thu, 7 Apr 2016 17:45:49 +0800 [thread overview]
Message-ID: <57062C4D.9040400@linux.intel.com> (raw)
In-Reply-To: <20160406170429.GP1924@sirena.org.uk>
On 04/07/2016 01:04 AM, Mark Brown wrote:
> On Wed, Apr 06, 2016 at 10:53:09AM +0200, Takashi Iwai wrote:
>
>> Han, one good advice is: be patient. This is no urgent fix, so there
>> is no many reason to rush too much with a pile of newer patchset.
>> Give some more time for other people to review.
> FWIW given that every one of the many versions of this series has got a
> bunch of review comments I've not looked at it yet...
>
Sorry, I'll slow down with more thinking.
BR,
Han
>
>
> _______________________________________________
> Alsa-devel mailing list
> Alsa-devel@alsa-project.org
> http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
next prev parent reply other threads:[~2016-04-07 9:44 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-06 7:29 [PATCH V7 0/2] ASoC: Add core API to register and cleanup DMI names for card han.lu
2016-04-06 7:29 ` [PATCH V7 1/2] ASoC: core: add API for registering and cleaning up DMI card names han.lu
2016-04-06 9:48 ` Takashi Sakamoto
2016-04-07 9:43 ` Han Lu
2016-04-06 7:29 ` [PATCH V7 2/2] ASoC: bytcr-rt5640: register DMI names for card han.lu
2016-04-06 8:53 ` [PATCH V7 0/2] ASoC: Add core API to register and cleanup " Takashi Iwai
2016-04-06 17:04 ` Mark Brown
2016-04-07 9:45 ` Han Lu [this message]
2016-04-07 9:33 ` Han Lu
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=57062C4D.9040400@linux.intel.com \
--to=han.lu@linux.intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=han.lu@intel.com \
--cc=liam.r.girdwood@linux.intel.com \
--cc=pierre-louis.bossart@linux.intel.com \
--cc=tiwai@suse.de \
--cc=vinod.koul@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;
as well as URLs for NNTP newsgroup(s).