From: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
To: "Amadeusz Sławiński" <amadeuszx.slawinski@linux.intel.com>,
"Mark Brown" <broonie@kernel.org>
Cc: Cezary Rojewski <cezary.rojewski@intel.com>,
Kai Vehmanen <kai.vehmanen@linux.intel.com>,
Peter Ujfalusi <peter.ujfalusi@linux.intel.com>,
alsa-devel@alsa-project.org, Takashi Iwai <tiwai@suse.com>,
Liam Girdwood <liam.r.girdwood@linux.intel.com>,
Ranjani Sridharan <ranjani.sridharan@linux.intel.com>,
Bard Liao <yung-chuan.liao@linux.intel.com>
Subject: Re: [PATCH 1/2] ASoC: Intel: boards: Fix typo in comments
Date: Mon, 24 Oct 2022 09:13:04 -0500 [thread overview]
Message-ID: <903eec24-3ea6-d4b1-3b3b-2a73770dca83@linux.intel.com> (raw)
In-Reply-To: <20221024190841.31572-2-amadeuszx.slawinski@linux.intel.com>
On 10/24/22 14:08, Amadeusz Sławiński wrote:
> It keeps propagating through machine boards, fix it once and for all.
>
> Reviewed-by: Cezary Rojewski <cezary.rojewski@intel.com>
> Signed-off-by: Amadeusz Sławiński <amadeuszx.slawinski@linux.intel.com>
Reviewed-by: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
> ---
> sound/soc/intel/boards/bdw-rt5650.c | 2 +-
> sound/soc/intel/boards/bdw-rt5677.c | 2 +-
> sound/soc/intel/boards/bxt_rt298.c | 2 +-
> sound/soc/intel/boards/bytcht_cx2072x.c | 2 +-
> sound/soc/intel/boards/bytcht_es8316.c | 2 +-
> sound/soc/intel/boards/bytcr_rt5640.c | 2 +-
> sound/soc/intel/boards/bytcr_rt5651.c | 2 +-
> sound/soc/intel/boards/bytcr_wm5102.c | 2 +-
> sound/soc/intel/boards/cht_bsw_max98090_ti.c | 2 +-
> sound/soc/intel/boards/cht_bsw_nau8824.c | 2 +-
> sound/soc/intel/boards/cht_bsw_rt5645.c | 2 +-
> sound/soc/intel/boards/cht_bsw_rt5672.c | 2 +-
> sound/soc/intel/boards/skl_nau88l25_max98357a.c | 2 +-
> sound/soc/intel/boards/skl_nau88l25_ssm4567.c | 2 +-
> 14 files changed, 14 insertions(+), 14 deletions(-)
next prev parent reply other threads:[~2022-10-24 15:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-24 19:08 [PATCH 0/2] ASoC: Intel: Fix typo in comments Amadeusz Sławiński
2022-10-24 19:08 ` [PATCH 1/2] ASoC: Intel: boards: " Amadeusz Sławiński
2022-10-24 14:13 ` Pierre-Louis Bossart [this message]
2022-10-24 19:08 ` [PATCH 2/2] ASoC: Intel: avs: " Amadeusz Sławiński
2022-10-26 19:04 ` [PATCH 0/2] ASoC: Intel: " 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=903eec24-3ea6-d4b1-3b3b-2a73770dca83@linux.intel.com \
--to=pierre-louis.bossart@linux.intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=amadeuszx.slawinski@linux.intel.com \
--cc=broonie@kernel.org \
--cc=cezary.rojewski@intel.com \
--cc=kai.vehmanen@linux.intel.com \
--cc=liam.r.girdwood@linux.intel.com \
--cc=peter.ujfalusi@linux.intel.com \
--cc=ranjani.sridharan@linux.intel.com \
--cc=tiwai@suse.com \
--cc=yung-chuan.liao@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