All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hans de Goede <hdegoede@redhat.com>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
	Mark Brown <broonie@kernel.org>,
	Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>,
	alsa-devel@alsa-project.org, linux-kernel@vger.kernel.org
Cc: Cezary Rojewski <cezary.rojewski@intel.com>,
	Liam Girdwood <liam.r.girdwood@linux.intel.com>,
	Jie Yang <yang.jie@linux.intel.com>,
	Jaroslav Kysela <perex@perex.cz>, Takashi Iwai <tiwai@suse.com>
Subject: Re: [PATCH v2 0/4] ASoC: Intel: bytcr_rt5640: few cleanups
Date: Sun, 10 Oct 2021 22:31:45 +0200	[thread overview]
Message-ID: <3219a8c9-a9c8-25a9-95df-9aa5dbdf6815@redhat.com> (raw)
In-Reply-To: <20211007165715.27463-1-andriy.shevchenko@linux.intel.com>

Hi,

On 10/7/21 6:57 PM, Andy Shevchenko wrote:
> The small set of cleanups against bytcr_rt5640 board file.
> 
> In v2:
> - added commit message to patch 2 (Joe, Pierre)
> - added cover letter (Pierre)
> - added Hans to Cc list (Hans)
> 
> 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.

Regards,

Hans



WARNING: multiple messages have this Message-ID (diff)
From: Hans de Goede <hdegoede@redhat.com>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
	Mark Brown <broonie@kernel.org>,
	Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>,
	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: Sun, 10 Oct 2021 22:31:45 +0200	[thread overview]
Message-ID: <3219a8c9-a9c8-25a9-95df-9aa5dbdf6815@redhat.com> (raw)
In-Reply-To: <20211007165715.27463-1-andriy.shevchenko@linux.intel.com>

Hi,

On 10/7/21 6:57 PM, Andy Shevchenko wrote:
> The small set of cleanups against bytcr_rt5640 board file.
> 
> In v2:
> - added commit message to patch 2 (Joe, Pierre)
> - added cover letter (Pierre)
> - added Hans to Cc list (Hans)
> 
> 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.

Regards,

Hans



  parent reply	other threads:[~2021-10-10 20:31 UTC|newest]

Thread overview: 15+ 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 ` 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   ` 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   ` 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   ` 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-07 16:57   ` Andy Shevchenko
2021-10-10 20:31 ` Hans de Goede [this message]
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
2021-10-11 17:01 ` Mark Brown
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=3219a8c9-a9c8-25a9-95df-9aa5dbdf6815@redhat.com \
    --to=hdegoede@redhat.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=broonie@kernel.org \
    --cc=cezary.rojewski@intel.com \
    --cc=liam.r.girdwood@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=perex@perex.cz \
    --cc=pierre-louis.bossart@linux.intel.com \
    --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 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.