From: broonie@kernel.org (Mark Brown)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2] ASoC: sun4i-i2s: move code from startup/shutdown hooks into pm_runtime hooks
Date: Sun, 21 Oct 2018 15:02:26 +0100 [thread overview]
Message-ID: <20181021140226.GF8554@sirena.org.uk> (raw)
In-Reply-To: <1716612.tSkIyEiKY2@anarsoul-thinkpad>
On Fri, Oct 19, 2018 at 09:18:18AM -0700, Vasily Khoruzhick wrote:
> On Wednesday, October 17, 2018 2:01:59 PM PDT Maxime Ripard wrote:
> > On Wed, Oct 17, 2018 at 08:36:26AM -0700, Vasily Khoruzhick wrote:
> > > On Wednesday, October 17, 2018 8:25:23 AM PDT Maxime Ripard wrote:
> > > > On Wed, Oct 17, 2018 at 07:41:55AM -0700, Vasily Khoruzhick wrote:
> > > > > On Wed, Oct 17, 2018 at 12:45 AM Maxime Ripard
Please delete unneeded context from mails when replying. Doing this
makes it much easier to find your reply in the message, helping ensure
it won't be missed by people scrolling through the irrelevant quoted
material.
> Mark, can you pick up this one please? Thanks!
Please resend, I dropped it due to the (initial) negative review
comments.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 488 bytes
Desc: not available
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20181021/b7ba89f4/attachment-0001.sig>
prev parent reply other threads:[~2018-10-21 14:02 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-16 3:11 [PATCH v2] ASoC: sun4i-i2s: move code from startup/shutdown hooks into pm_runtime hooks Vasily Khoruzhick
2018-10-16 7:16 ` Maxime Ripard
2018-10-17 3:08 ` Vasily Khoruzhick
2018-10-17 7:45 ` Maxime Ripard
2018-10-17 14:41 ` Vasily Khoruzhick
2018-10-17 15:25 ` Maxime Ripard
2018-10-17 15:36 ` Vasily Khoruzhick
2018-10-17 21:01 ` Maxime Ripard
2018-10-19 16:18 ` Vasily Khoruzhick
2018-10-21 14:02 ` 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=20181021140226.GF8554@sirena.org.uk \
--to=broonie@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
/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