From: Mark Brown <broonie@kernel.org>
To: Caesar Wang <wxt@rock-chips.com>
Cc: Sonny Rao <sonnyrao@chromium.org>,
Cheng-Yi Chiang <cychiang@chromium.org>,
Heiko Stuebner <heiko@sntech.de>,
zhengxing <zhengxing@rock-chips.com>,
"jay.xu" <xjq@rock-chips.com>,
linux-rockchip@lists.infradead.org,
linux-arm-kernel@lists.infradead.org,
dri-devel@lists.freedesktop.org, Jaroslav Kysela <perex@perex.cz>,
alsa-devel@alsa-project.org, Takashi Iwai <tiwai@suse.de>,
linux-kernel@vger.kernel.org, Dylan Reid <dgreid@chromium.org>,
Liam Girdwood <lgirdwood@gmail.com>,
Lars-Peter Clausen <lars@metafoo.de>,
Jarkko Nikula <jarkko.nikula@linux.intel.com>,
Tushar Behera <tushar.b@samsung.com>
Subject: Re: [PATCH 0/1] ASoC: max98090: add shutdown callback for max98090
Date: Wed, 8 Apr 2015 10:48:23 +0100 [thread overview]
Message-ID: <20150408094823.GR6023@sirena.org.uk> (raw)
In-Reply-To: <1428483128-23498-1-git-send-email-wxt@rock-chips.com>
[-- Attachment #1: Type: text/plain, Size: 535 bytes --]
On Wed, Apr 08, 2015 at 04:52:07PM +0800, Caesar Wang wrote:
>
> Tested on veyron devices,play music then shutdown device,here carefully
> to speaker or headphone.
>
>
>
> Caesar Wang (1):
> ASoC: max98090: add shutdown callback for max98090
Don't send cover letters for single patches, if there's anything that
needs saying it should either be in the changelog or after the --- in
the mail. If there's any content in the cover letter that's usually a
sign that the changelog on the actual patch needs improving.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
prev parent reply other threads:[~2015-04-08 9:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-08 8:52 Caesar Wang
2015-04-08 8:52 ` [PATCH] " Caesar Wang
2015-04-08 9:25 ` Heiko Stübner
2015-04-08 10:14 ` Caesar Wang
2015-04-08 9:50 ` Mark Brown
2015-04-08 10:15 ` Caesar Wang
2015-04-08 9:48 ` Mark Brown [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=20150408094823.GR6023@sirena.org.uk \
--to=broonie@kernel.org \
--cc=alsa-devel@alsa-project.org \
--cc=cychiang@chromium.org \
--cc=dgreid@chromium.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=heiko@sntech.de \
--cc=jarkko.nikula@linux.intel.com \
--cc=lars@metafoo.de \
--cc=lgirdwood@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=perex@perex.cz \
--cc=sonnyrao@chromium.org \
--cc=tiwai@suse.de \
--cc=tushar.b@samsung.com \
--cc=wxt@rock-chips.com \
--cc=xjq@rock-chips.com \
--cc=zhengxing@rock-chips.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
all inboxes | Powered by JetHome®