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 X-Spam-Level: X-Spam-Status: No, score=-4.0 required=3.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE, SPF_PASS autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 01235C433E0 for ; Wed, 15 Jul 2020 16:42:25 +0000 (UTC) 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 mail.kernel.org (Postfix) with ESMTPS id 7E94B20672 for ; Wed, 15 Jul 2020 16:42:24 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (1024-bit key) header.d=alsa-project.org header.i=@alsa-project.org header.b="NBaAEJtc" DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 7E94B20672 Authentication-Results: mail.kernel.org; dmarc=none (p=none dis=none) header.from=suse.de Authentication-Results: mail.kernel.org; spf=pass smtp.mailfrom=alsa-devel-bounces@alsa-project.org 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 F3A3D15E5; Wed, 15 Jul 2020 18:41:32 +0200 (CEST) DKIM-Filter: OpenDKIM Filter v2.11.0 alsa0.perex.cz F3A3D15E5 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=alsa-project.org; s=default; t=1594831343; bh=XTYGu8jBcE8fejJsN6HsQke1vSB+VEJmjRcOnOPetL4=; h=Date:From:To:Subject:In-Reply-To:References:Cc:List-Id: List-Unsubscribe:List-Archive:List-Post:List-Help:List-Subscribe: From; b=NBaAEJtcEca16MBfQiUi45lUH5z0LIIoVAPmbw8NPyrX2uWWcWfB1GGoXHe6RtTyP q0tumsusmajfTK7c1Zev+vH/q7Uqzd8Xi9DXtocCFPv2DT1nDPs/Kur2HKws2vxeqd 2ErqTc9nOvYm2KTgS++6ZZtbD4fIc4hdmSrh1Dy0= Received: from alsa1.perex.cz (localhost.localdomain [127.0.0.1]) by alsa1.perex.cz (Postfix) with ESMTP id 65A68F80217; Wed, 15 Jul 2020 18:41:32 +0200 (CEST) Received: by alsa1.perex.cz (Postfix, from userid 50401) id B10A5F8021D; Wed, 15 Jul 2020 18:41:30 +0200 (CEST) Received: from mx2.suse.de (mx2.suse.de [195.135.220.15]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by alsa1.perex.cz (Postfix) with ESMTPS id D44B3F80113 for ; Wed, 15 Jul 2020 18:41:20 +0200 (CEST) DKIM-Filter: OpenDKIM Filter v2.11.0 alsa1.perex.cz D44B3F80113 X-Virus-Scanned: by amavisd-new at test-mx.suse.de Received: from relay2.suse.de (unknown [195.135.221.27]) by mx2.suse.de (Postfix) with ESMTP id BEAD2AF83; Wed, 15 Jul 2020 16:41:23 +0000 (UTC) Date: Wed, 15 Jul 2020 18:41:19 +0200 Message-ID: From: Takashi Iwai To: Pierre-Louis Bossart Subject: Re: [PATCH 01/10] ALSA: Replace the word "slave" in vmaster API In-Reply-To: References: <20200714172631.25371-1-tiwai@suse.de> <20200714172631.25371-2-tiwai@suse.de> User-Agent: Wanderlust/2.15.9 (Almost Unreal) SEMI/1.14.6 (Maruoka) FLIM/1.14.9 (=?UTF-8?B?R29qxY0=?=) APEL/10.8 Emacs/25.3 (x86_64-suse-linux-gnu) MULE/6.0 (HANACHIRUSATO) MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka") Content-Type: text/plain; charset=US-ASCII Cc: alsa-devel@alsa-project.org 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 Wed, 15 Jul 2020 16:34:51 +0200, Pierre-Louis Bossart wrote: > > > > >> On 7/14/20 12:26 PM, Takashi Iwai wrote: > >>> Follow the recent inclusive terminology guidelines and replace the > >>> word "slave" in vmaster API. I chose the word "replica" at this time > >>> since it seems fitting for the purpose. > >> > >> Thanks Takashi for starting this. > >> > >> For the HDaudio Volume widgets, the spec says they may have different > >> step size but use the same number of steps, so they are not copy-exact > >> versions in the usual 'replica' sense but rather follow or track the > >> master configuration. > >> > >> The internal guidance I see at Intel is to use 'replica' mainly in a > >> database/configuration management context. > >> > >> If the idea is that the 'replicas' use the same configuration as the > >> 'master', that'd be fine indeed but we may want to add a clarifying > >> comment that the end-result may be different for each 'replica'? > > > > I don't mind to pick up another word. > > What could be another better alternative? > > I don't have a suggestion that is really better. the usual suggestions > of 'secondary' or 'subordinate' are not really great in this context, > something like 'tracker' or 'follower' might work but are maybe more > vague for controls. "Follower" would fit for the purpose, I think. (Or better to say "retweeter"? :) > I am really fine with 'replica', just wanted to clarify that it's not > doing the same thing in multiple places but using the same > configuration in multiple places. Yeah point taken. thanks, Takashi