linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Rafael J. Wysocki" <rafael@kernel.org>
To: Jilin Yuan <yuanjilin@cdjrlc.com>
Cc: Amit Kachhap <amit.kachhap@gmail.com>,
	Daniel Lezcano <daniel.lezcano@linaro.org>,
	Viresh Kumar <viresh.kumar@linaro.org>,
	Lukasz Luba <lukasz.luba@arm.com>,
	"Rafael J. Wysocki" <rafael@kernel.org>,
	Amit Kucheria <amitk@kernel.org>,
	"Zhang, Rui" <rui.zhang@intel.com>,
	Linux PM <linux-pm@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] drivers/thermal: fix repeated words in comments
Date: Sat, 3 Sep 2022 19:56:51 +0200	[thread overview]
Message-ID: <CAJZ5v0idwPoK_VoHXTNr+eGzq8+d2=Y0v1sxS7NmwX-PkvNSBA@mail.gmail.com> (raw)
In-Reply-To: <20220822123239.28400-1-yuanjilin@cdjrlc.com>

On Mon, Aug 22, 2022 at 2:32 PM Jilin Yuan <yuanjilin@cdjrlc.com> wrote:
>
>  Delete the redundant word 'device'.
>  Delete the redundant word 'which'.
>
> Signed-off-by: Jilin Yuan <yuanjilin@cdjrlc.com>
> ---
>  drivers/thermal/cpufreq_cooling.c | 2 +-
>  drivers/thermal/thermal_of.c      | 2 +-
>  2 files changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/thermal/cpufreq_cooling.c b/drivers/thermal/cpufreq_cooling.c
> index b8151d95a806..13551b386e72 100644
> --- a/drivers/thermal/cpufreq_cooling.c
> +++ b/drivers/thermal/cpufreq_cooling.c
> @@ -495,7 +495,7 @@ static struct thermal_cooling_device_ops cpufreq_cooling_ops = {
>
>  /**
>   * __cpufreq_cooling_register - helper function to create cpufreq cooling device
> - * @np: a valid struct device_node to the cooling device device tree node
> + * @np: a valid struct device_node to the cooling device tree node
>   * @policy: cpufreq policy
>   * Normally this should be same as cpufreq policy->related_cpus.
>   * @em: Energy Model of the cpufreq policy
> diff --git a/drivers/thermal/thermal_of.c b/drivers/thermal/thermal_of.c
> index b65d435cb92f..91bbed308305 100644
> --- a/drivers/thermal/thermal_of.c
> +++ b/drivers/thermal/thermal_of.c
> @@ -651,7 +651,7 @@ EXPORT_SYMBOL_GPL(devm_thermal_zone_of_sensor_register);
>  /**
>   * devm_thermal_zone_of_sensor_unregister - Resource managed version of
>   *                             thermal_zone_of_sensor_unregister().
> - * @dev: Device for which which resource was allocated.
> + * @dev: Device for which resource was allocated.
>   * @tzd: a pointer to struct thermal_zone_device where the sensor is registered.
>   *
>   * This function removes the sensor callbacks and private data from the
> --

Applied (as 6.1 material) under edited subject and with rewritten changelog.

Thanks!

      reply	other threads:[~2022-09-03 17:57 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-22 12:32 [PATCH] drivers/thermal: fix repeated words in comments Jilin Yuan
2022-09-03 17:56 ` Rafael J. Wysocki [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='CAJZ5v0idwPoK_VoHXTNr+eGzq8+d2=Y0v1sxS7NmwX-PkvNSBA@mail.gmail.com' \
    --to=rafael@kernel.org \
    --cc=amit.kachhap@gmail.com \
    --cc=amitk@kernel.org \
    --cc=daniel.lezcano@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=lukasz.luba@arm.com \
    --cc=rui.zhang@intel.com \
    --cc=viresh.kumar@linaro.org \
    --cc=yuanjilin@cdjrlc.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 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).