From: Nicolin Chen <b42378@freescale.com>
To: Mark Brown <broonie@kernel.org>
Cc: Linus Walleij <linus.walleij@linaro.org>,
"alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
Wolfram Sang <wsa@the-dreams.de>
Subject: Re: Is that reasonable to support pinctrl PM in ASoC core?
Date: Fri, 25 Oct 2013 10:21:11 +0800 [thread overview]
Message-ID: <20131025022110.GE8385@MrMyself> (raw)
In-Reply-To: <20131024141524.GH18506@sirena.org.uk>
On Thu, Oct 24, 2013 at 03:15:24PM +0100, Mark Brown wrote:
> On Thu, Oct 24, 2013 at 03:19:03PM +0200, Linus Walleij wrote:
> As we discussed in person earlier how about we merge this on a subsystem
> basis and then once we've established what the pattern really is we
> think about putting it into the core. Nicolin, do you want to write a
> patch for this?
I'd like to, sir.
Thank you,
Nicolin Chen
next prev parent reply other threads:[~2013-10-25 2:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-24 11:07 Is that reasonable to support pinctrl PM in ASoC core? Nicolin Chen
2013-10-24 11:52 ` Mark Brown
2013-10-24 13:19 ` Linus Walleij
2013-10-24 14:15 ` Mark Brown
2013-10-25 2:21 ` Nicolin Chen [this message]
2013-10-25 10:00 ` Nicolin Chen
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=20131025022110.GE8385@MrMyself \
--to=b42378@freescale.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=linus.walleij@linaro.org \
--cc=wsa@the-dreams.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 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.