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 31E53C43334 for ; Mon, 13 Jun 2022 10:03:39 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S234660AbiFMKDh (ORCPT ); Mon, 13 Jun 2022 06:03:37 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:41598 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S241426AbiFMKCr (ORCPT ); Mon, 13 Jun 2022 06:02:47 -0400 Received: from smtp-out1.suse.de (smtp-out1.suse.de [195.135.220.28]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id A48C32DE7 for ; Mon, 13 Jun 2022 03:02:37 -0700 (PDT) Received: from imap2.suse-dmz.suse.de (imap2.suse-dmz.suse.de [192.168.254.74]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-521) server-digest SHA512) (No client certificate requested) by smtp-out1.suse.de (Postfix) with ESMTPS id 7337121C9E; Mon, 13 Jun 2022 10:02:36 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=suse.de; s=susede2_rsa; t=1655114556; h=from:from:reply-to:date:date:message-id:message-id:to:to:cc:cc: mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=cCnURu5VkrKkhOwy6eVBLJZSyOr4bhRv1ONxGXEQi/o=; b=sLiiv+S7CG8JJ4sbxVeVkFpG7BoM7lGJIrjXnUv3K8iuo6euYMu02dD9ktZE7vmWau7Hwp lg2sTP5554YsekdV7zMd7rxVHqusDzXw3aWLJwyTF1JA1wl9bx4hZSRjvopUB0sOxnfecA IVMdx4qDIhy+ozToUnQx/yenTRAXQz4= DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/relaxed; d=suse.de; s=susede2_ed25519; t=1655114556; h=from:from:reply-to:date:date:message-id:message-id:to:to:cc:cc: mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=cCnURu5VkrKkhOwy6eVBLJZSyOr4bhRv1ONxGXEQi/o=; b=YR9k7chXn4J5sVeWHrmCF3/EtK8jS9TCiLB+vtX9KuM3krZXZGqcr1pEjNdWVEBA+Kc7rc PvZwZoMNOwZJD0Aw== Received: from imap2.suse-dmz.suse.de (imap2.suse-dmz.suse.de [192.168.254.74]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-521) server-digest SHA512) (No client certificate requested) by imap2.suse-dmz.suse.de (Postfix) with ESMTPS id 4AC1613443; Mon, 13 Jun 2022 10:02:36 +0000 (UTC) Received: from dovecot-director2.suse.de ([192.168.254.65]) by imap2.suse-dmz.suse.de with ESMTPSA id s2t9ETwLp2JiVQAAMHmgww (envelope-from ); Mon, 13 Jun 2022 10:02:36 +0000 Date: Mon, 13 Jun 2022 12:02:35 +0200 Message-ID: <87fsk898zo.wl-tiwai@suse.de> From: Takashi Iwai To: Raghu Ballappa Bankapur Cc: Jaroslav Kysela , Takashi Iwai , "Liam Girdwood" , Mark Brown , , , Krishna Jha Subject: Re: [PATCH V0 1/1] asoc: msm: use hashtable to check kcontrol In-Reply-To: <6b665002-b68e-5392-a7ff-908a1c853663@quicinc.com> References: <8735gsznnt.wl-tiwai@suse.de> <874k0tnjkw.wl-tiwai@suse.de> <6b665002-b68e-5392-a7ff-908a1c853663@quicinc.com> User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/27.2 Mule/6.0 MIME-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue") Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, 13 Jun 2022 11:19:05 +0200, Raghu Ballappa Bankapur wrote: > > Hi Takashi > > v2 patch looks fine. Can we use this patch to submit to android common > kernel? There is code freeze for KMI on june 17. If nothing reported, I'm going to merge the v3 patch (already posted) to for-next branch for 5.19 kernel in this week. Let's see :) thanks, Takashi > > Please share your opinion. > > > Thanks > > Raghu Bankapur > > On 6/10/2022 11:31 AM, Takashi Iwai wrote: > > On Thu, 09 Jun 2022 20:16:52 +0200, > > Raghu Ballappa Bankapur wrote: > >> > >> Hi Takashi > >> > >> Our implementation also falls inline with your approach  [PATCH RFC] ALSA: > >> control: Use xarray for faster lookups (kernel.org), but you approach looks to > >> be clean with xarray. > >> > >> is it possible to upstream those changes? > > I submitted a v2 patch, please check it out. > > > > > > thanks, > > > > Takashi > 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 alsa0.perex.cz (alsa0.perex.cz [77.48.224.243]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id 27784C43334 for ; Mon, 13 Jun 2022 10:03:34 +0000 (UTC) Received: from alsa1.perex.cz (alsa1.perex.cz [207.180.221.201]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by alsa0.perex.cz (Postfix) with ESMTPS id DBC911817; Mon, 13 Jun 2022 12:02:42 +0200 (CEST) DKIM-Filter: OpenDKIM Filter v2.11.0 alsa0.perex.cz DBC911817 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=alsa-project.org; s=default; t=1655114612; bh=SBdQI377Ld2NTfZ1Ecol4us42ZTF5fOpOUq8HxfvYzA=; h=Date:From:To:Subject:In-Reply-To:References:Cc:List-Id: List-Unsubscribe:List-Archive:List-Post:List-Help:List-Subscribe: From; b=IEPYUvL15Y31QZALahpmjFKAHZCNknUCqpk7Gjr2Cc3Jaa+iDaz84OLDotBqxIbA1 iSFW7kN4NkNeNX8ToSjG0+4cdC2mb7chPlMUkQFyfc9J6rgI4N52DgU+iZemJmoJ0Y RFbbnDad7pB2mXcGbLKsAexm04/f0bJggUybx9fo= Received: from alsa1.perex.cz (localhost.localdomain [127.0.0.1]) by alsa1.perex.cz (Postfix) with ESMTP id 7EEFCF80139; Mon, 13 Jun 2022 12:02:42 +0200 (CEST) Received: by alsa1.perex.cz (Postfix, from userid 50401) id D9ED4F804C1; Mon, 13 Jun 2022 12:02:40 +0200 (CEST) Received: from smtp-out1.suse.de (smtp-out1.suse.de [195.135.220.28]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by alsa1.perex.cz (Postfix) with ESMTPS id 772DBF800D8 for ; Mon, 13 Jun 2022 12:02:36 +0200 (CEST) DKIM-Filter: OpenDKIM Filter v2.11.0 alsa1.perex.cz 772DBF800D8 Authentication-Results: alsa1.perex.cz; dkim=pass (1024-bit key) header.d=suse.de header.i=@suse.de header.b="sLiiv+S7"; dkim=permerror (0-bit key) header.d=suse.de header.i=@suse.de header.b="YR9k7chX" Received: from imap2.suse-dmz.suse.de (imap2.suse-dmz.suse.de [192.168.254.74]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-521) server-digest SHA512) (No client certificate requested) by smtp-out1.suse.de (Postfix) with ESMTPS id 7337121C9E; Mon, 13 Jun 2022 10:02:36 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=suse.de; s=susede2_rsa; t=1655114556; h=from:from:reply-to:date:date:message-id:message-id:to:to:cc:cc: mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=cCnURu5VkrKkhOwy6eVBLJZSyOr4bhRv1ONxGXEQi/o=; b=sLiiv+S7CG8JJ4sbxVeVkFpG7BoM7lGJIrjXnUv3K8iuo6euYMu02dD9ktZE7vmWau7Hwp lg2sTP5554YsekdV7zMd7rxVHqusDzXw3aWLJwyTF1JA1wl9bx4hZSRjvopUB0sOxnfecA IVMdx4qDIhy+ozToUnQx/yenTRAXQz4= DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/relaxed; d=suse.de; s=susede2_ed25519; t=1655114556; h=from:from:reply-to:date:date:message-id:message-id:to:to:cc:cc: mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=cCnURu5VkrKkhOwy6eVBLJZSyOr4bhRv1ONxGXEQi/o=; b=YR9k7chXn4J5sVeWHrmCF3/EtK8jS9TCiLB+vtX9KuM3krZXZGqcr1pEjNdWVEBA+Kc7rc PvZwZoMNOwZJD0Aw== Received: from imap2.suse-dmz.suse.de (imap2.suse-dmz.suse.de [192.168.254.74]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-521) server-digest SHA512) (No client certificate requested) by imap2.suse-dmz.suse.de (Postfix) with ESMTPS id 4AC1613443; Mon, 13 Jun 2022 10:02:36 +0000 (UTC) Received: from dovecot-director2.suse.de ([192.168.254.65]) by imap2.suse-dmz.suse.de with ESMTPSA id s2t9ETwLp2JiVQAAMHmgww (envelope-from ); Mon, 13 Jun 2022 10:02:36 +0000 Date: Mon, 13 Jun 2022 12:02:35 +0200 Message-ID: <87fsk898zo.wl-tiwai@suse.de> From: Takashi Iwai To: Raghu Ballappa Bankapur Subject: Re: [PATCH V0 1/1] asoc: msm: use hashtable to check kcontrol In-Reply-To: <6b665002-b68e-5392-a7ff-908a1c853663@quicinc.com> References: <8735gsznnt.wl-tiwai@suse.de> <874k0tnjkw.wl-tiwai@suse.de> <6b665002-b68e-5392-a7ff-908a1c853663@quicinc.com> User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/27.2 Mule/6.0 MIME-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue") Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Cc: alsa-devel@alsa-project.org, linux-kernel@vger.kernel.org, Liam Girdwood , Takashi Iwai , Mark Brown , Krishna Jha X-BeenThere: alsa-devel@alsa-project.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: "Alsa-devel mailing list for ALSA developers - http://www.alsa-project.org" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: alsa-devel-bounces@alsa-project.org Sender: "Alsa-devel" On Mon, 13 Jun 2022 11:19:05 +0200, Raghu Ballappa Bankapur wrote: > > Hi Takashi > > v2 patch looks fine. Can we use this patch to submit to android common > kernel? There is code freeze for KMI on june 17. If nothing reported, I'm going to merge the v3 patch (already posted) to for-next branch for 5.19 kernel in this week. Let's see :) thanks, Takashi > > Please share your opinion. > > > Thanks > > Raghu Bankapur > > On 6/10/2022 11:31 AM, Takashi Iwai wrote: > > On Thu, 09 Jun 2022 20:16:52 +0200, > > Raghu Ballappa Bankapur wrote: > >> > >> Hi Takashi > >> > >> Our implementation also falls inline with your approach  [PATCH RFC] ALSA: > >> control: Use xarray for faster lookups (kernel.org), but you approach looks to > >> be clean with xarray. > >> > >> is it possible to upstream those changes? > > I submitted a v2 patch, please check it out. > > > > > > thanks, > > > > Takashi >