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 B515EC4167B for ; Sun, 10 Dec 2023 15:56:26 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S232680AbjLJPuE (ORCPT ); Sun, 10 Dec 2023 10:50:04 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:33328 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229584AbjLJPuC (ORCPT ); Sun, 10 Dec 2023 10:50:02 -0500 Received: from madrid.collaboradmins.com (madrid.collaboradmins.com [IPv6:2a00:1098:ed:100::25]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 5F09FB4; Sun, 10 Dec 2023 07:50:08 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=collabora.com; s=mail; t=1702223406; bh=VGe9TdQ/vud/OfN67E3dqBDKZmGPAhkf1qflgqRvIos=; h=Date:Subject:To:Cc:References:From:In-Reply-To:From; b=UNpdqagg0CxJdPA7a1TACKFRVtJ0lMgkrjkyEPXRoSMH0rZxNCxWE7OW4AswJGp36 aU3FmVAMORs3cY+OGG/KrivzAZ8+8TOb+CD5JeaydY17nG9LIBfGBZBUYMri3R/fxm /ML5Glcelo5SsqXw23LVFOwy37lB9utJJOVGdGNOjpT8BFppWwJxUkLuJZeZobyraA unn8EBL+9CpZcXHvQet6VmbecGAH3z2cZpl1IwEdKUZ6VdUVaInnQDL83rkCe7oA+y Cx9xc+C4A8CGImdDkTtqJkxcqEn2x6k8+HROy53STcfp+pz65pU8mB7RC5TCoedj49 sHfhRL7KWvwWg== Received: from [100.115.223.179] (cola.collaboradmins.com [195.201.22.229]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) (Authenticated sender: cristicc) by madrid.collaboradmins.com (Postfix) with ESMTPSA id 3281337813EF; Sun, 10 Dec 2023 15:50:05 +0000 (UTC) Message-ID: <5095ce7b-13bd-4805-b81e-f7565ab41b67@collabora.com> Date: Sun, 10 Dec 2023 17:50:04 +0200 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: [PATCH 11/11] ASoC: SOF: topology: Add new DAI type entry for SOF_DAI_AMD_BT Content-Language: en-US To: Mark Brown Cc: Venkata Prasad Potturu , Liam Girdwood , Jaroslav Kysela , Takashi Iwai , Pierre-Louis Bossart , Peter Ujfalusi , Bard Liao , Ranjani Sridharan , Daniel Baluta , Kai Vehmanen , Alper Nebi Yasak , Syed Saba Kareem , Kuninori Morimoto , Marian Postevca , Vijendar Mukunda , V sujith kumar Reddy , Mastan Katragadda , Ajit Kumar Pandey , linux-sound@vger.kernel.org, linux-kernel@vger.kernel.org, sound-open-firmware@alsa-project.org, kernel@collabora.com References: <20231209205351.880797-1-cristian.ciocaltea@collabora.com> <20231209205351.880797-12-cristian.ciocaltea@collabora.com> <318470ce-1631-4c46-b425-755c877dda65@amd.com> <421128f7-6a17-4be9-a72b-272ea4017fbd@collabora.com> From: Cristian Ciocaltea In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 12/10/23 16:01, Mark Brown wrote: > On Sun, Dec 10, 2023 at 12:12:53PM +0200, Cristian Ciocaltea wrote: >> On 12/10/23 11:51, Venkata Prasad Potturu wrote: > >>> This should send to SOF git repo for rewiew, once SOF reviewers approved >>> this, again need to send to broonie git. >>> All the changes in sound/soc/sof/ path should go to SOF git. > >> Unfortunately I'm not familiar with the SOF dev workflow. So it's not >> enough to have this patch cc-ed to sound-open-firmware@alsa-project.org? > > The SOF people basically do their own thing in github at > > https://github.com/thesofproject/linux > > with a github workflow and submit their patches upstream in batches a > few times a release, however my understanding is that their workflow can > cope with things going in directly upstream as well. Thanks for clarifying, Mark! That would greatly simplify and speedup the whole process, at least for trivial patches like this one.