All of lore.kernel.org
 help / color / mirror / Atom feed
From: Viresh Kumar <viresh.kumar@linaro.org>
To: Hector Yuan <hector.yuan@mediatek.com>
Cc: linux-mediatek@lists.infradead.org,
	linux-arm-kernel@lists.infradead.org, linux-pm@vger.kernel.org,
	"Rafael J. Wysocki" <rjw@rjwysocki.net>,
	linux-kernel@vger.kernel.org, wsd_upstream@mediatek.com
Subject: Re: [PATCH v1 1/1] cpufreq:Fix parameter in parse_perf_domain
Date: Tue, 5 Oct 2021 09:51:28 +0530	[thread overview]
Message-ID: <20211005042128.o47qximtibgak33q@vireshk-i7> (raw)
In-Reply-To: <1633358553-2842-2-git-send-email-hector.yuan@mediatek.com>

On 04-10-21, 22:42, Hector Yuan wrote:
> From: "Hector.Yuan" <hector.yuan@mediatek.com>
> 
> Should pass per-cpu id to map perf_domain for related_cpus
> rather than map policy_cpu several times.
> 
> Signed-off-by: Hector.Yuan <hector.yuan@mediatek.com>
> ---
>  include/linux/cpufreq.h |    2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/include/linux/cpufreq.h b/include/linux/cpufreq.h
> index ff88bb3..66a1f49 100644
> --- a/include/linux/cpufreq.h
> +++ b/include/linux/cpufreq.h
> @@ -1041,7 +1041,7 @@ static inline int of_perf_domain_get_sharing_cpumask(int pcpu, const char *list_
>  		if (cpu == pcpu)
>  			continue;
>  
> -		ret = parse_perf_domain(pcpu, list_name, cell_name);
> +		ret = parse_perf_domain(cpu, list_name, cell_name);
>  		if (ret < 0)
>  			continue;

Applied. Thanks.

-- 
viresh

WARNING: multiple messages have this Message-ID (diff)
From: Viresh Kumar <viresh.kumar@linaro.org>
To: Hector Yuan <hector.yuan@mediatek.com>
Cc: linux-mediatek@lists.infradead.org,
	linux-arm-kernel@lists.infradead.org, linux-pm@vger.kernel.org,
	"Rafael J. Wysocki" <rjw@rjwysocki.net>,
	linux-kernel@vger.kernel.org, wsd_upstream@mediatek.com
Subject: Re: [PATCH v1 1/1] cpufreq:Fix parameter in parse_perf_domain
Date: Tue, 5 Oct 2021 09:51:28 +0530	[thread overview]
Message-ID: <20211005042128.o47qximtibgak33q@vireshk-i7> (raw)
In-Reply-To: <1633358553-2842-2-git-send-email-hector.yuan@mediatek.com>

On 04-10-21, 22:42, Hector Yuan wrote:
> From: "Hector.Yuan" <hector.yuan@mediatek.com>
> 
> Should pass per-cpu id to map perf_domain for related_cpus
> rather than map policy_cpu several times.
> 
> Signed-off-by: Hector.Yuan <hector.yuan@mediatek.com>
> ---
>  include/linux/cpufreq.h |    2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/include/linux/cpufreq.h b/include/linux/cpufreq.h
> index ff88bb3..66a1f49 100644
> --- a/include/linux/cpufreq.h
> +++ b/include/linux/cpufreq.h
> @@ -1041,7 +1041,7 @@ static inline int of_perf_domain_get_sharing_cpumask(int pcpu, const char *list_
>  		if (cpu == pcpu)
>  			continue;
>  
> -		ret = parse_perf_domain(pcpu, list_name, cell_name);
> +		ret = parse_perf_domain(cpu, list_name, cell_name);
>  		if (ret < 0)
>  			continue;

Applied. Thanks.

-- 
viresh

_______________________________________________
Linux-mediatek mailing list
Linux-mediatek@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-mediatek

WARNING: multiple messages have this Message-ID (diff)
From: Viresh Kumar <viresh.kumar@linaro.org>
To: Hector Yuan <hector.yuan@mediatek.com>
Cc: linux-mediatek@lists.infradead.org,
	linux-arm-kernel@lists.infradead.org, linux-pm@vger.kernel.org,
	"Rafael J. Wysocki" <rjw@rjwysocki.net>,
	linux-kernel@vger.kernel.org, wsd_upstream@mediatek.com
Subject: Re: [PATCH v1 1/1] cpufreq:Fix parameter in parse_perf_domain
Date: Tue, 5 Oct 2021 09:51:28 +0530	[thread overview]
Message-ID: <20211005042128.o47qximtibgak33q@vireshk-i7> (raw)
In-Reply-To: <1633358553-2842-2-git-send-email-hector.yuan@mediatek.com>

On 04-10-21, 22:42, Hector Yuan wrote:
> From: "Hector.Yuan" <hector.yuan@mediatek.com>
> 
> Should pass per-cpu id to map perf_domain for related_cpus
> rather than map policy_cpu several times.
> 
> Signed-off-by: Hector.Yuan <hector.yuan@mediatek.com>
> ---
>  include/linux/cpufreq.h |    2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/include/linux/cpufreq.h b/include/linux/cpufreq.h
> index ff88bb3..66a1f49 100644
> --- a/include/linux/cpufreq.h
> +++ b/include/linux/cpufreq.h
> @@ -1041,7 +1041,7 @@ static inline int of_perf_domain_get_sharing_cpumask(int pcpu, const char *list_
>  		if (cpu == pcpu)
>  			continue;
>  
> -		ret = parse_perf_domain(pcpu, list_name, cell_name);
> +		ret = parse_perf_domain(cpu, list_name, cell_name);
>  		if (ret < 0)
>  			continue;

Applied. Thanks.

-- 
viresh

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2021-10-05  4:21 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-04 14:42 [PATCH v1] cpufreq: Fix parameter in parse_perf_domain Hector Yuan
2021-10-04 14:42 ` Hector Yuan
2021-10-04 14:42 ` Hector Yuan
2021-10-04 14:42 ` [PATCH v1 1/1] cpufreq:Fix " Hector Yuan
2021-10-04 14:42   ` Hector Yuan
2021-10-04 14:42   ` Hector Yuan
2021-10-05  4:21   ` Viresh Kumar [this message]
2021-10-05  4:21     ` Viresh Kumar
2021-10-05  4:21     ` Viresh Kumar

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=20211005042128.o47qximtibgak33q@vireshk-i7 \
    --to=viresh.kumar@linaro.org \
    --cc=hector.yuan@mediatek.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mediatek@lists.infradead.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=rjw@rjwysocki.net \
    --cc=wsd_upstream@mediatek.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.