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>,
	Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>,
	Mark Brown <broonie@kernel.org>,
	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 v4 0/4] ASoC: Intel: bytcht_es8316: few cleanups
Date: Sun, 10 Oct 2021 22:31:15 +0200	[thread overview]
Message-ID: <9206ba12-c69f-c638-31ed-9f15ca0e6587@redhat.com> (raw)
In-Reply-To: <20211007164523.27094-1-andriy.shevchenko@linux.intel.com>

Hi,

On 10/7/21 6:45 PM, Andy Shevchenko wrote:
> The small set of cleanups against bytcht_es8316 board file.
> 
> In v4:
> - fixed Pierre's email (Pierre)
> - added Hans to the Cc list
> 
> In v3:
> - actually added a Pierre's tag (Mark)
> 
> In v2:
> - added tag (Pierre)
> - added commit message to the patch 2 (Joe)
> 
> Andy Shevchenko (4):
>   ASoC: Intel: bytcht_es8316: Get platform data via dev_get_platdata()
>   ASoC: Intel: bytcht_es8316: Use temporary variable for struct device
>   ASoC: Intel: bytcht_es8316: Switch to use gpiod_get_optional()
>   ASoC: Intel: bytcht_es8316: Utilize dev_err_probe() to avoid log
>     saturation

Thanks, the entire series good to me:

Reviewed-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>,
	Pierre-Louis Bossart <pierre-louis.bossart@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 v4 0/4] ASoC: Intel: bytcht_es8316: few cleanups
Date: Sun, 10 Oct 2021 22:31:15 +0200	[thread overview]
Message-ID: <9206ba12-c69f-c638-31ed-9f15ca0e6587@redhat.com> (raw)
In-Reply-To: <20211007164523.27094-1-andriy.shevchenko@linux.intel.com>

Hi,

On 10/7/21 6:45 PM, Andy Shevchenko wrote:
> The small set of cleanups against bytcht_es8316 board file.
> 
> In v4:
> - fixed Pierre's email (Pierre)
> - added Hans to the Cc list
> 
> In v3:
> - actually added a Pierre's tag (Mark)
> 
> In v2:
> - added tag (Pierre)
> - added commit message to the patch 2 (Joe)
> 
> Andy Shevchenko (4):
>   ASoC: Intel: bytcht_es8316: Get platform data via dev_get_platdata()
>   ASoC: Intel: bytcht_es8316: Use temporary variable for struct device
>   ASoC: Intel: bytcht_es8316: Switch to use gpiod_get_optional()
>   ASoC: Intel: bytcht_es8316: Utilize dev_err_probe() to avoid log
>     saturation

Thanks, the entire series good to me:

Reviewed-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: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-07 16:45 [PATCH v4 0/4] ASoC: Intel: bytcht_es8316: few cleanups Andy Shevchenko
2021-10-07 16:45 ` Andy Shevchenko
2021-10-07 16:45 ` [PATCH v4 1/4] ASoC: Intel: bytcht_es8316: Get platform data via dev_get_platdata() Andy Shevchenko
2021-10-07 16:45   ` Andy Shevchenko
2021-10-07 16:45 ` [PATCH v4 2/4] ASoC: Intel: bytcht_es8316: Use temporary variable for struct device Andy Shevchenko
2021-10-07 16:45   ` Andy Shevchenko
2021-10-07 16:45 ` [PATCH v4 3/4] ASoC: Intel: bytcht_es8316: Switch to use gpiod_get_optional() Andy Shevchenko
2021-10-07 16:45   ` Andy Shevchenko
2021-10-07 16:45 ` [PATCH v4 4/4] ASoC: Intel: bytcht_es8316: Utilize dev_err_probe() to avoid log saturation Andy Shevchenko
2021-10-07 16:45   ` Andy Shevchenko
2021-10-10 20:31 ` Hans de Goede [this message]
2021-10-10 20:31   ` [PATCH v4 0/4] ASoC: Intel: bytcht_es8316: few cleanups Hans de Goede

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=9206ba12-c69f-c638-31ed-9f15ca0e6587@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.