Received: by 2002:a05:6902:102b:0:0:0:0 with SMTP id x11csp521686ybt; Mon, 6 Jul 2020 15:29:26 -0700 (PDT) X-Google-Smtp-Source: ABdhPJxpeaWPJE/4aYTykvUfojE2OJP6PcOXl5N57jm9k/BQSFEOnwr/rwJ54nPJdSf3U917nKJR X-Received: by 2002:a05:6402:3113:: with SMTP id dc19mr57079909edb.20.1594074566018; Mon, 06 Jul 2020 15:29:26 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1594074566; cv=none; d=google.com; s=arc-20160816; b=Vwz9PYwt66c+RyiRS+ba9oPqq07CNko0j5ra3yaLYZQjn6apbLL3HIM0bHGSRM+eNl e4QsqFTKeyK3iv1tpBR83CytBpO7tzyjjK+X3184tGuqygu91wSEheWyscjLN6Qjh/f2 VkoOO+BQrKz/qWVyZKIEiLkz6cRsk2sOA7bWZt1AKaBp4Idb6Hy2Cus9J8mFatYjkCKD mzrbnmyWCNgoZOiJmbdChLYUsNfEak9jniCY7Kvr9+ZU8Y7I9vGmToDf2sU1vDyEsAld lhxd3XGAMHgGgYDZ1ZCUKSMV5YHre3RGPu/0xouFJU1CDxGcLKTAvrxYxZe06OAwF81Q wteA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding:mime-version :references:in-reply-to:message-id:subject:cc:to:from:date; bh=39qkM3Ec1bONIDNAteEgX0HzhuqbPW2bcChG+3cIBsM=; b=qS/zx4mscPrqpElkDgxifC3GJCzWq72uSbkC7N29vDqC/4WvhCIJuMq0km8GNkTEZX vlO876VtqGKCrVlq5IPf4kQ0fF3pdhoOTosE3+//t1QWhBgEz60bmXi7Rucb770rPLqD HjkfD3YZDjWSE5azQJsjcEzmWZXmv+8S9BMIrQZfJ22DBkJz5b9FFuuHMbYNrNk8IHZw HW/C3YBqumTz160F87G/oEAb5N3JYy2F+/Xn8f36m3RPad+CzUhmloQTUOBeVujQHxL+ QkuBBcoClLp5RDrshF7p45E3+ihscukJml3yffGHIvDhNtuMD2iXPKcrD26hy2e3U0g0 wXQg== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id w4si13366478ejj.300.2020.07.06.15.29.02; Mon, 06 Jul 2020 15:29:25 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726889AbgGFW2W (ORCPT + 99 others); Mon, 6 Jul 2020 18:28:22 -0400 Received: from mail.kernel.org ([198.145.29.99]:46500 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726763AbgGFW2W (ORCPT ); Mon, 6 Jul 2020 18:28:22 -0400 Received: from oasis.local.home (cpe-66-24-58-225.stny.res.rr.com [66.24.58.225]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id 2D5EF206E9; Mon, 6 Jul 2020 22:28:21 +0000 (UTC) Date: Mon, 6 Jul 2020 18:28:19 -0400 From: Steven Rostedt To: Pavel Begunkov Cc: Dan Williams , ksummit-discuss@lists.linuxfoundation.org, Greg Kroah-Hartman , linux-kernel@vger.kernel.org, tech-board-discuss@lists.linuxfoundation.org, Chris Mason , torvalds@linux-foundation.org Subject: Re: [Tech-board-discuss] [PATCH] CodingStyle: Inclusive Terminology Message-ID: <20200706182819.3467fa32@oasis.local.home> In-Reply-To: <717030b7-ecba-2ca4-39ff-6a5a04a732d4@gmail.com> References: <159389297140.2210796.13590142254668787525.stgit@dwillia2-desk3.amr.corp.intel.com> <1cceba0f-c8ad-260d-9a09-5417bee32d50@gmail.com> <20200706181052.174c290a@oasis.local.home> <717030b7-ecba-2ca4-39ff-6a5a04a732d4@gmail.com> X-Mailer: Claws Mail 3.17.3 (GTK+ 2.24.32; x86_64-pc-linux-gnu) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, 7 Jul 2020 01:17:47 +0300 Pavel Begunkov wrote: > Totally agree with you! But do we care then whether two _devices_ or _objects_ > are slave-master? Can't see how it fundamentally differs. The term slave carries a lot more meaning than subordinate. I replied to someone else but later realized that the person sent me their reply offlist, so my reply to them was also offlist. What I told them was, back in college (decades ago), when I first mentioned "master/slave" in conversation (I think it was about hard drives), a person in that conversation stated that those were not very nice terms to use. I blew it off back then, but after listening to more people, I found that using "slave" even to describe a device is not something that people care to hear about. And in actuality, does one device actually enslave another device? I think that terminology is misleading to begin with. -- Steve