All of lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel Lezcano <daniel.lezcano@linaro.org>
To: rafael@kernel.org, andriy.shevchenko@linux.intel.com
Cc: linux-kernel@vger.kernel.org, Zhang Rui <rui.zhang@intel.com>,
	Amit Kucheria <amitk@kernel.org>,
	linux-pm@vger.kernel.org (open list:THERMAL)
Subject: [PATCH v2 2/9] thermal/drivers/devfreq_cooling: Use HZ macros
Date: Wed, 24 Feb 2021 15:42:12 +0100	[thread overview]
Message-ID: <20210224144222.23762-2-daniel.lezcano@linaro.org> (raw)
In-Reply-To: <20210224144222.23762-1-daniel.lezcano@linaro.org>

HZ unit conversion macros are available in units.h, use them and
remove the duplicate definition.

Signed-off-by: Daniel Lezcano <daniel.lezcano@linaro.org>
Reviewed-by: Christian Eggers <ceggers@arri.de>
---
 drivers/thermal/devfreq_cooling.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/drivers/thermal/devfreq_cooling.c b/drivers/thermal/devfreq_cooling.c
index fed3121ff2a1..fa5b8b0c7604 100644
--- a/drivers/thermal/devfreq_cooling.c
+++ b/drivers/thermal/devfreq_cooling.c
@@ -19,10 +19,10 @@
 #include <linux/pm_opp.h>
 #include <linux/pm_qos.h>
 #include <linux/thermal.h>
+#include <linux/units.h>
 
 #include <trace/events/thermal.h>
 
-#define HZ_PER_KHZ		1000
 #define SCALE_ERROR_MITIGATION	100
 
 static DEFINE_IDA(devfreq_ida);
-- 
2.17.1


  reply	other threads:[~2021-02-24 15:25 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-24 14:42 [PATCH v2 1/9] units: Add the HZ macros Daniel Lezcano
2021-02-24 14:42 ` Daniel Lezcano [this message]
2021-02-24 14:42 ` [PATCH v2 3/9] devfreq: Use " Daniel Lezcano
2021-02-26  6:08   ` Chanwoo Choi
2021-02-26  8:51     ` Daniel Lezcano
2021-02-26  9:14       ` Chanwoo Choi
2021-02-24 14:42 ` [PATCH v2 4/9] iio/drivers/as73211: " Daniel Lezcano
2021-03-14 16:59   ` Jonathan Cameron
2021-02-24 14:42 ` [PATCH v2 5/9] hwmon/drivers/mr75203: " Daniel Lezcano
2021-03-11 21:44   ` Guenter Roeck
2021-02-24 14:42 ` [PATCH v2 6/9] iio/drivers/hid-sensor: " Daniel Lezcano
2021-03-14 17:00   ` Jonathan Cameron
2021-02-24 14:42 ` [PATCH v2 7/9] i2c/drivers/ov02q10: " Daniel Lezcano
2021-02-24 14:42 ` [PATCH v2 8/9] mtd/drivers/nand: " Daniel Lezcano
2021-02-24 14:42   ` Daniel Lezcano
2021-03-02 16:31   ` Miquel Raynal
2021-03-02 16:31     ` Miquel Raynal
2021-03-02 17:03     ` Daniel Lezcano
2021-03-02 17:03       ` Daniel Lezcano
2021-03-02 17:12       ` Miquel Raynal
2021-03-02 17:12         ` Miquel Raynal
2021-02-24 14:42 ` [PATCH v2 9/9] phy/drivers/stm32: " Daniel Lezcano
2021-02-24 14:42   ` Daniel Lezcano
2021-03-02 16:32   ` Vinod Koul
2021-03-02 16:32     ` Vinod Koul
2021-03-02 17:03     ` Daniel Lezcano
2021-03-02 17:03       ` Daniel Lezcano
2021-03-03  5:40       ` Vinod Koul
2021-03-03  5:40         ` Vinod Koul
2021-03-03  6:09         ` Daniel Lezcano
2021-03-03  6:09           ` Daniel Lezcano
2021-02-24 14:52 ` [PATCH v2 1/9] units: Add the " Daniel Lezcano
2021-02-25 11:22 ` Andy Shevchenko
2021-03-19  8:08   ` Daniel Lezcano
2021-05-10 12:59 ` Andy Shevchenko
2021-07-12 16:34 ` Andy Shevchenko
2021-07-15 14:03   ` Daniel Lezcano

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=20210224144222.23762-2-daniel.lezcano@linaro.org \
    --to=daniel.lezcano@linaro.org \
    --cc=amitk@kernel.org \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=rafael@kernel.org \
    --cc=rui.zhang@intel.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.