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'?
[...]
/*
- * link slave - this contains a slave control element
+ * link replica - this contains a replica control element
*
* It fakes the control callbacsk with additional attenuation by the
unrelated typo here that maybe we can fix while we are at it?
- * master control. A slave may have either one or two channels.
+ * master control. A replica may have either one or two channels.
*/
