From: Mark Brown <broonie@kernel.org>
To: Ladislav Michl <ladis@linux-mips.org>
Cc: alsa-devel@alsa-project.org,
Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>,
anish kumar <yesanishhere@gmail.com>
Subject: Re: [PATCH 2/5] ASoC: max9867: Fix power management
Date: Wed, 28 Nov 2018 09:22:53 +0000 [thread overview]
Message-ID: <20181128092253.GC6828@sirena.org.uk> (raw)
In-Reply-To: <20181127173727.GA23636@lenoch>
[-- Attachment #1.1: Type: text/plain, Size: 417 bytes --]
On Tue, Nov 27, 2018 at 06:37:27PM +0100, Ladislav Michl wrote:
> On Mon, Nov 26, 2018 at 12:57:19PM +0000, Mark Brown wrote:
> > > While here move suspend and resume functions to more common place.
> > It would be better to split this out from the rest of the change as it's
> > a fairly large bit of code motion relative to the rest of the patch.
> So something like this is preffered solution? (untested)
Yes.
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
next prev parent reply other threads:[~2018-11-28 9:22 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-23 14:25 [PATCH 0/5] max9867 driver update Ladislav Michl
2018-11-23 14:27 ` [PATCH 1/5] ASoC: max9867: Fix whitespace Ladislav Michl
2018-11-26 17:20 ` Applied "ASoC: max9867: Fix whitespace" to the asoc tree Mark Brown
2018-11-23 14:27 ` [PATCH 2/5] ASoC: max9867: Fix power management Ladislav Michl
2018-11-26 12:57 ` Mark Brown
2018-11-27 17:37 ` Ladislav Michl
2018-11-28 9:22 ` Mark Brown [this message]
2018-11-23 14:27 ` [PATCH 3/5] ASoC: max9867: Calculate LRCLK divider Ladislav Michl
2018-11-23 14:28 ` [PATCH 4/5] ASoC: max9867: Fix signal paths Ladislav Michl
2018-11-23 14:28 ` [PATCH 5/5] ASoC: max9867: Add copyright and module author Ladislav Michl
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=20181128092253.GC6828@sirena.org.uk \
--to=broonie@kernel.org \
--cc=alsa-devel@alsa-project.org \
--cc=kuninori.morimoto.gx@renesas.com \
--cc=ladis@linux-mips.org \
--cc=yesanishhere@gmail.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 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.