From: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
To: Mark Brown <broonie@kernel.org>
Cc: tiwai@suse.de, alsa-devel@alsa-project.org,
Rander Wang <rander.wang@linux.intel.com>,
Kai Vehmanen <kai.vehmanen@linux.intel.com>
Subject: Re: [PATCH v2 1/6] ASoC: codecs: max98373: split I2C and common parts
Date: Wed, 8 Jul 2020 08:01:01 -0500 [thread overview]
Message-ID: <017f1c40-bb24-f98e-fe67-620b4d66bcb8@linux.intel.com> (raw)
In-Reply-To: <20200708113828.GI4655@sirena.org.uk>
On 7/8/20 6:38 AM, Mark Brown wrote:
> On Tue, Jul 07, 2020 at 03:57:35PM -0500, Pierre-Louis Bossart wrote:
>> To prepare support for SoundWire, let's first split the I2C and common
>> parts. No new functionality, just indents and formatting to make
>> checkpatch happy.
>
> You've got a couple of fixes after this patch, the fixes should've been
> first.
ok, will respin them.
next prev parent reply other threads:[~2020-07-08 13:02 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-07 20:57 [PATCH v2 0/6] ASoC: codecs: add MAX98373 Soundwire driver Pierre-Louis Bossart
2020-07-07 20:57 ` [PATCH v2 1/6] ASoC: codecs: max98373: split I2C and common parts Pierre-Louis Bossart
2020-07-08 11:38 ` Mark Brown
2020-07-08 13:01 ` Pierre-Louis Bossart [this message]
2020-07-07 20:57 ` [PATCH v2 2/6] ASoC: codecs: max98373: Removed superfluous volume control from chip default Pierre-Louis Bossart
2020-07-07 20:57 ` [PATCH v2 3/6] ASoc: codecs: max98373: remove Idle_bias_on to let codec suspend Pierre-Louis Bossart
2020-07-07 20:57 ` [PATCH v2 4/6] ASoC: codecs: max98373: add SoundWire support Pierre-Louis Bossart
2020-07-07 20:57 ` [PATCH v2 5/6] ASoC: Intel: sof-sdw: add MAX98373 I2C dependencies Pierre-Louis Bossart
2020-07-07 20:57 ` [PATCH v2 6/6] ASoC: Intel: sdw_max98373: add card_late_probe support Pierre-Louis Bossart
2020-07-08 11:48 ` Mark Brown
2020-07-08 13:01 ` Pierre-Louis Bossart
2020-07-08 16:59 ` [PATCH v2 0/6] ASoC: codecs: add MAX98373 Soundwire driver Mark Brown
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=017f1c40-bb24-f98e-fe67-620b4d66bcb8@linux.intel.com \
--to=pierre-louis.bossart@linux.intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=kai.vehmanen@linux.intel.com \
--cc=rander.wang@linux.intel.com \
--cc=tiwai@suse.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox