Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:18 as permitted sender) client-ip=2620:137:e000::1:18;
From:   Mark Brown <broonie@kernel.org>
To:     ajye.huang@gmail.com, linux-kernel@vger.kernel.org
Cc:     mac.chiang@intel.com, vamshi.krishna.gopal@intel.com,
        daniel.baluta@nxp.com, Jaroslav Kysela <perex@perex.cz>,
        ranjani.sridharan@linux.intel.com, yung-chuan.liao@linux.intel.com,
        sound-open-firmware@alsa-project.org, alsa-devel@alsa-project.org,
        Takashi Iwai <tiwai@suse.com>, yang.jie@linux.intel.com,
        yong.zhi@intel.com, liam.r.girdwood@linux.intel.com,
        pierre-louis.bossart@linux.intel.com, kai.vehmanen@linux.intel.com,
        brent.lu@intel.com, ajye_huang@compal.corp-partner.google.com,
        cezary.rojewski@intel.com
In-Reply-To: <20220324084708.2009375-1-ajye_huang@compal.corp-partner.google.com>
References: <20220324084708.2009375-1-ajye_huang@compal.corp-partner.google.com>
Subject: Re: [PATCH v1] ASoC: Intel: sof_rt5682: Add support for max98360a speaker amp on SSP2
Message-Id: <164932429462.3844153.4809967512345990079.b4-ty@kernel.org>
Date:   Thu, 07 Apr 2022 10:38:14 +0100
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
Precedence: bulk

On Thu, 24 Mar 2022 16:47:08 +0800, Ajye Huang wrote:
> Follow Intel's design to replace max98360a amp SSP2 reather than SSP1
> by judging DMI_OEM_STRING in sof_rt5682_quirk_table struct.
> And reusing max98357's topology since DAI setting could be leveraged.
> 
> 

Applied to

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

Thanks!

[1/1] ASoC: Intel: sof_rt5682: Add support for max98360a speaker amp on SSP2
      commit: fcd1e39cca6e3a262f2badfcd5edd76c910ad3bc

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