alsa-devel.alsa-project.org archive mirror
 help / color / mirror / Atom feed
From: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
To: Takashi Iwai <tiwai@suse.de>
Cc: alsa-devel@alsa-project.org
Subject: Re: [PATCH 01/10] ALSA: Replace the word "slave" in vmaster API
Date: Wed, 15 Jul 2020 09:34:51 -0500	[thread overview]
Message-ID: <a93460a3-ac0e-be0b-7c46-47b87fd611c2@linux.intel.com> (raw)
In-Reply-To: <s5h5zaptgaz.wl-tiwai@suse.de>



>> 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.

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.

  reply	other threads:[~2020-07-15 14:49 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-14 17:26 [PATCH 00/10] ALSA: Replace words for inclusive terminalogy guideline Takashi Iwai
2020-07-14 17:26 ` [PATCH 01/10] ALSA: Replace the word "slave" in vmaster API Takashi Iwai
2020-07-14 18:52   ` Pierre-Louis Bossart
2020-07-15  6:59     ` Takashi Iwai
2020-07-15 14:34       ` Pierre-Louis Bossart [this message]
2020-07-15 16:41         ` Takashi Iwai
2020-07-14 17:26 ` [PATCH 02/10] ALSA: ac97: Replace the words white/blacklist Takashi Iwai
2020-07-14 17:26 ` [PATCH 03/10] ALSA: bt87x: " Takashi Iwai
2020-07-14 17:26 ` [PATCH 04/10] ALSA: ctxfi: Replace the word blacklist Takashi Iwai
2020-07-14 17:26 ` [PATCH 05/10] ALSA: es1968: Replace the words white/blacklist Takashi Iwai
2020-07-14 17:26 ` [PATCH 06/10] ALSA: hda: " Takashi Iwai
2020-07-14 17:26 ` [PATCH 07/10] ALSA: intel8x0: " Takashi Iwai
2020-07-14 17:26 ` [PATCH 08/10] ALSA: nm256: Replace the words blacklist Takashi Iwai
2020-07-14 17:26 ` [PATCH 09/10] ALSA: via82xx: Replace the words whitelist Takashi Iwai
2020-07-14 17:26 ` [PATCH 10/10] ALSA: usb-audio: Replace blacklist word Takashi Iwai
2020-07-15 17:04   ` Alexander Tsoy
2020-07-15 17:20     ` Takashi Iwai

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=a93460a3-ac0e-be0b-7c46-47b87fd611c2@linux.intel.com \
    --to=pierre-louis.bossart@linux.intel.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=tiwai@suse.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).