[0/2] ASoC: remove disable_route_checks

Message

Kuninori Morimoto Jan. 9, 2025, 12:13 a.m. UTC

Hi Mark, Intel test team

ASoC framwork has disable_route_checks flag. Intel is the last user of it,
but it seems it exists in dead code. So we can remove it.

But I can't test it. This patch needs Intel team's Tested-by.

Kuninori Morimoto (2):
  ASoC: intel: remove disable_route_checks
  ASoC: remove disable_route_checks

 include/sound/soc.h                          |  1 -
 sound/soc/intel/boards/skl_hda_dsp_generic.c |  2 --
 sound/soc/soc-core.c                         | 29 +++-----------------
 sound/soc/soc-topology.c                     | 12 ++------
 4 files changed, 6 insertions(+), 38 deletions(-)

Comments

Amadeusz Sławiński Jan. 9, 2025, 1:45 p.m. UTC | #1

On 1/9/2025 1:13 AM, Kuninori Morimoto wrote:
> 
> Hi Mark, Intel test team
> 
> ASoC framwork has disable_route_checks flag. Intel is the last user of it,
> but it seems it exists in dead code. So we can remove it.
> 
> But I can't test it. This patch needs Intel team's Tested-by.
> 

Not sure what's there to test, when it removes unused code ;). Still I 
did quick test, current solution (avs driver) works fine with regards to 
core/topology changes.

Tested-by: Amadeusz Sławiński <[e-mail]>

Mark Brown Jan. 9, 2025, 6:06 p.m. UTC | #2

On Thu, 09 Jan 2025 00:13:56 +0000, Kuninori Morimoto wrote:
> ASoC framwork has disable_route_checks flag. Intel is the last user of it,
> but it seems it exists in dead code. So we can remove it.
> 
> But I can't test it. This patch needs Intel team's Tested-by.
> 
> Kuninori Morimoto (2):
>   ASoC: intel: remove disable_route_checks
>   ASoC: remove disable_route_checks
> 
> [...]

Applied to

   https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-next

Thanks!

[1/2] ASoC: intel: remove disable_route_checks
      commit: 61aff2da3e63a43f22e60aa1bc57026ce07d189e
[2/2] ASoC: remove disable_route_checks
      commit: 9c0e29b9957e407af6197ff1fb48f365a9b0c248

All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) and sent to Linus during
the next merge window (or sooner if it is a bug fix), however if
problems are discovered then the patch may be dropped or reverted.

You may get further e-mails resulting from automated or manual testing
and review of the tree, please engage with people reporting problems and
send followup patches addressing any issues that are reported if needed.

If any updates are required or you are submitting further changes they
should be sent as incremental updates against current git, existing
patches will not be replaced.

Please add any relevant lists and maintainers to the CCs when replying
to this mail.

Thanks,
Mark