From: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
To: Hans de Goede <hdegoede@redhat.com>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Mark Brown <broonie@kernel.org>,
alsa-devel@alsa-project.org, linux-kernel@vger.kernel.org
Cc: Liam Girdwood <liam.r.girdwood@linux.intel.com>,
Cezary Rojewski <cezary.rojewski@intel.com>,
Jie Yang <yang.jie@linux.intel.com>,
Takashi Iwai <tiwai@suse.com>
Subject: Re: [PATCH v2 0/4] ASoC: Intel: bytcr_rt5640: few cleanups
Date: Mon, 11 Oct 2021 09:19:01 -0500 [thread overview]
Message-ID: <d4e5aca7-9ec1-6421-c3b5-b03983bd1bb5@linux.intel.com> (raw)
In-Reply-To: <3219a8c9-a9c8-25a9-95df-9aa5dbdf6815@redhat.com>
>> Andy Shevchenko (4):
>> ASoC: Intel: bytcr_rt5640: Get platform data via dev_get_platdata()
>> ASoC: Intel: bytcr_rt5640: Use temporary variable for struct device
>> ASoC: Intel: bytcr_rt5640: use devm_clk_get_optional() for mclk
>> ASoC: Intel: bytcr_rt5640: Utilize dev_err_probe() to avoid log
>> saturation
>
> Thanks, the entire series good to me, this one I've also
> given a quick test-spin, so:
>
> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
> Tested-by: Hans de Goede <hdegoede@redhat.com>
>
> For the series.
Acked-by: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
next prev parent reply other threads:[~2021-10-11 16:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-07 16:57 [PATCH v2 0/4] ASoC: Intel: bytcr_rt5640: few cleanups Andy Shevchenko
2021-10-07 16:57 ` [PATCH v2 1/4] ASoC: Intel: bytcr_rt5640: Get platform data via dev_get_platdata() Andy Shevchenko
2021-10-07 16:57 ` [PATCH v2 2/4] ASoC: Intel: bytcr_rt5640: Use temporary variable for struct device Andy Shevchenko
2021-10-07 16:57 ` [PATCH v2 3/4] ASoC: Intel: bytcr_rt5640: use devm_clk_get_optional() for mclk Andy Shevchenko
2021-10-07 16:57 ` [PATCH v2 4/4] ASoC: Intel: bytcr_rt5640: Utilize dev_err_probe() to avoid log saturation Andy Shevchenko
2021-10-10 20:31 ` [PATCH v2 0/4] ASoC: Intel: bytcr_rt5640: few cleanups Hans de Goede
2021-10-11 14:19 ` Pierre-Louis Bossart [this message]
2021-10-11 17:01 ` 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=d4e5aca7-9ec1-6421-c3b5-b03983bd1bb5@linux.intel.com \
--to=pierre-louis.bossart@linux.intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=broonie@kernel.org \
--cc=cezary.rojewski@intel.com \
--cc=hdegoede@redhat.com \
--cc=liam.r.girdwood@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tiwai@suse.com \
--cc=yang.jie@linux.intel.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