Linux Sound subsystem development
 help / color / mirror / Atom feed
From: "Amadeusz Sławiński" <amadeuszx.slawinski@linux.intel.com>
To: Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>,
	Mark Brown <broonie@kernel.org>
Cc: alsa-devel@alsa-project.org, linux-sound@vger.kernel.org
Subject: Re: [PATCH v2 04/13] ASoC: intel: remove dpcm_xxx flags
Date: Mon, 30 Sep 2024 11:44:56 +0200	[thread overview]
Message-ID: <7b4ddfa0-193e-44a1-a039-1f2fdea0923d@linux.intel.com> (raw)
In-Reply-To: <87ldz9lwgl.wl-kuninori.morimoto.gx@renesas.com>

On 9/30/2024 4:14 AM, Kuninori Morimoto wrote:
> dpcm_xxx flags are no longer needed. It converts dpcm_xxx flag to
> xxx_only if needed.
> 
> Signed-off-by: Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>
> ---
>   sound/soc/intel/avs/boards/da7219.c        | 2 --
>   sound/soc/intel/avs/boards/dmic.c          | 4 ++--
>   sound/soc/intel/avs/boards/es8336.c        | 2 --
>   sound/soc/intel/avs/boards/hdaudio.c       | 4 ----
>   sound/soc/intel/avs/boards/i2s_test.c      | 2 --
>   sound/soc/intel/avs/boards/max98357a.c     | 2 +-
>   sound/soc/intel/avs/boards/max98373.c      | 2 --
>   sound/soc/intel/avs/boards/max98927.c      | 2 --
>   sound/soc/intel/avs/boards/nau8825.c       | 2 --
>   sound/soc/intel/avs/boards/rt274.c         | 2 --
>   sound/soc/intel/avs/boards/rt286.c         | 2 --
>   sound/soc/intel/avs/boards/rt298.c         | 2 --
>   sound/soc/intel/avs/boards/rt5514.c        | 2 +-
>   sound/soc/intel/avs/boards/rt5663.c        | 2 --
>   sound/soc/intel/avs/boards/rt5682.c        | 2 --
>   sound/soc/intel/avs/boards/ssm4567.c       | 2 --
>   sound/soc/intel/boards/sof_board_helpers.c | 2 --

That's a bit of weird split, sof_board_helpers.c should've probably been 
with the rest of SOF boards in patch 10? ;)


  reply	other threads:[~2024-09-30  9:45 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-30  2:13 [PATCH v2 00/13] ASoC: remove dpcm_xxx flags Kuninori Morimoto
2024-09-30  2:13 ` [PATCH v2 01/13] ASoC: amd: " Kuninori Morimoto
2024-09-30  2:13 ` [PATCH v2 02/13] ASoC: fsl: " Kuninori Morimoto
2024-09-30  2:13 ` [PATCH v2 03/13] ASoC: sof: " Kuninori Morimoto
2024-09-30  2:14 ` [PATCH v2 04/13] ASoC: intel: " Kuninori Morimoto
2024-09-30  9:44   ` Amadeusz Sławiński [this message]
2024-10-01  0:43     ` Kuninori Morimoto
2024-09-30  2:14 ` [PATCH v2 05/13] ASoC: samsung: " Kuninori Morimoto
2024-09-30  2:14 ` [PATCH v2 06/13] ASoC: mediatek: " Kuninori Morimoto
2024-09-30  2:14 ` [PATCH v2 07/13] ASoC: soc-core: " Kuninori Morimoto
2024-09-30  2:14 ` [PATCH v2 08/13] ASoC: soc-compress: " Kuninori Morimoto
2024-09-30  2:14 ` [PATCH v2 09/13] ASoC: soc-topology: " Kuninori Morimoto
2024-09-30  2:14 ` [PATCH v2 10/13] ASoC: intel: boards: " Kuninori Morimoto
2024-09-30  2:14 ` [PATCH v2 11/13] ASoC: soc-pcm: " Kuninori Morimoto
2024-09-30  2:14 ` [PATCH v2 12/13] ASoC: doc: " Kuninori Morimoto
2024-09-30  2:14 ` [PATCH v2 13/13] ASoC: soc-pcm: merge DPCM and non-DPCM validation check Kuninori Morimoto

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=7b4ddfa0-193e-44a1-a039-1f2fdea0923d@linux.intel.com \
    --to=amadeuszx.slawinski@linux.intel.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@kernel.org \
    --cc=kuninori.morimoto.gx@renesas.com \
    --cc=linux-sound@vger.kernel.org \
    /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