From: Joe Perches <joe@perches.com>
To: Kees Cook <keescook@chromium.org>,
"Rafael J. Wysocki" <rjw@rjwysocki.net>,
Ulf Hansson <ulf.hansson@linaro.org>
Cc: Kevin Hilman <khilman@kernel.org>, Pavel Machek <pavel@ucw.cz>,
Len Brown <len.brown@intel.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Jan Kiszka <jan.kiszka@siemens.com>,
Kieran Bingham <kbingham@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Stephen Boyd <sboyd@kernel.org>,
Leonard Crestez <leonard.crestez@nxp.com>,
linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] genpd: Fix up terminology with parent/child
Date: Fri, 10 Jul 2020 10:13:51 -0700 [thread overview]
Message-ID: <db753175946cf53e77999d1fbb3cf949f777ef61.camel@perches.com> (raw)
In-Reply-To: <202007081629.0840B4CB78@keescook>
On Wed, 2020-07-08 at 16:32 -0700, Kees Cook wrote:
> The genpd infrastructure uses the terms master/slave, but such uses have
> no external exposures (not even in Documentation/driver-api/pm/*) and are
> not mandated by nor associated with any external specifications. Change
> the language used through-out to parent/child.
Thanks.
Perhaps change a couple more references:
$ grep -i -P '(?:master|slave)' drivers/cpuidle/cpuidle-psci-domain.c
/* Link genpd masters/subdomains to model the CPU topology. */
$ grep -i -P '(?:master|slave)' drivers/opp/core.c
* genpd and its master have one to one mapping of performance states
prev parent reply other threads:[~2020-07-10 17:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-08 23:32 [PATCH v2] genpd: Fix up terminology with parent/child Kees Cook
2020-07-09 8:22 ` Greg Kroah-Hartman
2020-07-09 8:48 ` Kieran Bingham
2020-07-09 12:25 ` Rafael J. Wysocki
2020-07-10 9:28 ` Ulf Hansson
2020-07-10 16:41 ` Kevin Hilman
2020-07-10 17:13 ` Joe Perches [this message]
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=db753175946cf53e77999d1fbb3cf949f777ef61.camel@perches.com \
--to=joe@perches.com \
--cc=akpm@linux-foundation.org \
--cc=gregkh@linuxfoundation.org \
--cc=jan.kiszka@siemens.com \
--cc=kbingham@kernel.org \
--cc=keescook@chromium.org \
--cc=khilman@kernel.org \
--cc=len.brown@intel.com \
--cc=leonard.crestez@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=pavel@ucw.cz \
--cc=rjw@rjwysocki.net \
--cc=sboyd@kernel.org \
--cc=ulf.hansson@linaro.org \
/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).