From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id B6EC5C4332F for ; Fri, 8 Apr 2022 14:47:13 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S237148AbiDHOtP (ORCPT ); Fri, 8 Apr 2022 10:49:15 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:54314 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S235102AbiDHOtN (ORCPT ); Fri, 8 Apr 2022 10:49:13 -0400 Received: from ams.source.kernel.org (ams.source.kernel.org [145.40.68.75]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id B1FE864FE; Fri, 8 Apr 2022 07:47:09 -0700 (PDT) Received: from smtp.kernel.org (relay.kernel.org [52.25.139.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ams.source.kernel.org (Postfix) with ESMTPS id B4275B82B7D; Fri, 8 Apr 2022 14:47:07 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id CA850C385A1; Fri, 8 Apr 2022 14:47:03 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1649429226; bh=VQX066yFGsYa8X9WFsJ18Wdtsul1sn0pOjLIbhD9EZM=; h=From:To:Cc:In-Reply-To:References:Subject:Date:From; b=YBZKwm24jHCmwQeoOUonaVdSZ/osYDmAwV/8h1o54UnPhyw2WpqlJSQ3CCr+aFqSl b1jdUX1L5QmRQxCVUO6rG71d3VweqZl6ofDxEXKTeaykWYZut3bTFw87zVpH9/NiRZ 9Nb9Yi3WxOSVpETRs+niqtEux1jxd1i3pF5WYRHSAqytDduInnOdsQfz8XB9SirFE4 enXRnysDd8oXue+QE8yw8th6NJAI6w34xGtceiSu/dEenroWIIAycCd6mxmbsQy5Bi CkWsm9EgPfIrWDrLHC6BOIwlQRRLZ7nA03R3lv4BrkVgeEswxsOLvH3l29HlTBSFrl lIJYdf4yqwL1g== From: Mark Brown To: tzungbi@google.com, robh+dt@kernel.org, jiaxin.yu@mediatek.com Cc: trevor.wu@mediatek.com, linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org, aaronyu@google.com, matthias.bgg@gmail.com, alsa-devel@alsa-project.org, linux-mediatek@lists.infradead.org, devicetree@vger.kernel.org, linmq006@gmail.com, Project_Global_Chrome_Upstream_Group@mediatek.com, angelogioacchino.delregno@collabora.com In-Reply-To: <20220402051754.17513-1-jiaxin.yu@mediatek.com> References: <20220402051754.17513-1-jiaxin.yu@mediatek.com> Subject: Re: [v8 0/4] ASoC: mediatek: mt8192: support rt1015p_rt5682s Message-Id: <164942922353.1424253.18184837371560126158.b4-ty@kernel.org> Date: Fri, 08 Apr 2022 15:47:03 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Sat, 2 Apr 2022 13:17:50 +0800, Jiaxin Yu wrote: > The series reuses mt8192-mt6359-rt10150rt5682.c for supporting machine > driver with rt1015p speaker amplifier and rt5682s headset codec. > > Changes from v7: > - "mediatek,hdmi-codec" is an optional property, the code and the > binding document should match. > > [...] Applied to https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-next Thanks! [1/4] ASoC: dt-bindings: mt8192-mt6359: add new compatible and new properties commit: 1efe7eca170d344c5101c69ac51df6982de764e4 [2/4] ASoC: mediatek: mt8192: refactor for I2S3 DAI link of speaker commit: e1e408e60e856b99782b26308a9dc3937b1ba8bf [3/4] ASoC: mediatek: mt8192: refactor for I2S8/I2S9 DAI links of headset commit: f8910fb4985a00c0a1e6932dc5bda6181c549b76 [4/4] ASoC: mediatek: mt8192: support rt1015p_rt5682s commit: 7a80167b08f52e7b5eaa18a9d515efdcff9085fc 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