mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Randy Dunlap <rdunlap@infradead.org>
To: Aubrey Li <aubrey.li@intel.com>,
	lizefan@huawei.com, tj@kernel.org, hannes@cmpxchg.org
Cc: linux-kernel@vger.kernel.org, Aubrey Li <aubrey.li@linux.intel.com>
Subject: Re: [PATCH] cpuset: fix typos in comments
Date: Tue, 12 Jan 2021 20:33:54 -0800	[thread overview]
Message-ID: <df087a62-ae0d-d7f9-890c-792adabfc77a@infradead.org> (raw)
In-Reply-To: <1610512661-135383-1-git-send-email-aubrey.li@intel.com>

On 1/12/21 8:37 PM, Aubrey Li wrote:
> Change hierachy to hierarchy and congifured to configured, no functionality
> changed.
> 
> Signed-off-by: Aubrey Li <aubrey.li@linux.intel.com>

Reviewed-by: Randy Dunlap <rdunlap@infradead.org>

Thanks.

> ---
>  kernel/cgroup/cpuset.c | 6 +++---
>  1 file changed, 3 insertions(+), 3 deletions(-)
> 
> diff --git a/kernel/cgroup/cpuset.c b/kernel/cgroup/cpuset.c
> index 57b5b5d..15f4300 100644
> --- a/kernel/cgroup/cpuset.c
> +++ b/kernel/cgroup/cpuset.c
> @@ -98,7 +98,7 @@ struct cpuset {
>  	 * and if it ends up empty, it will inherit the parent's mask.
>  	 *
>  	 *
> -	 * On legacy hierachy:
> +	 * On legacy hierarchy:
>  	 *
>  	 * The user-configured masks are always the same with effective masks.
>  	 */
> @@ -1286,10 +1286,10 @@ static int update_parent_subparts_cpumask(struct cpuset *cpuset, int cmd,
>   * @cs:  the cpuset to consider
>   * @tmp: temp variables for calculating effective_cpus & partition setup
>   *
> - * When congifured cpumask is changed, the effective cpumasks of this cpuset
> + * When configured cpumask is changed, the effective cpumasks of this cpuset
>   * and all its descendants need to be updated.
>   *
> - * On legacy hierachy, effective_cpus will be the same with cpu_allowed.
> + * On legacy hierarchy, effective_cpus will be the same with cpu_allowed.
>   *
>   * Called with cpuset_mutex held
>   */
> 


-- 
~Randy
You can't do anything without having to do something else first.
-- Belefant's Law

  reply	other threads:[~2021-01-13  4:34 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-13  4:37 Aubrey Li
2021-01-13  4:33 ` Randy Dunlap [this message]
2021-01-15 20:37 ` Tejun Heo

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=df087a62-ae0d-d7f9-890c-792adabfc77a@infradead.org \
    --to=rdunlap@infradead.org \
    --cc=aubrey.li@intel.com \
    --cc=aubrey.li@linux.intel.com \
    --cc=hannes@cmpxchg.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lizefan@huawei.com \
    --cc=tj@kernel.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

all inboxes | Powered by JetHome®