mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Daniel Lezcano <daniel.lezcano@linaro.org>
To: daniel.lezcano@linaro.org, rafael@kernel.org
Cc: rui.zhang@intel.com, linux-pm@vger.kernel.org,
	linux-kernel@vger.kernel.org, thierry.reding@gmail.com
Subject: [PATCH v1 0/3] Move the thermal zone device structure in private header
Date: Tue, 18 Apr 2023 10:30:52 +0200	[thread overview]
Message-ID: <20230418083055.3611721-1-daniel.lezcano@linaro.org> (raw)

The following series applies on top of the changes:

https://lore.kernel.org/all/20230413114647.3878792-1-daniel.lezcano@linaro.org/

There is no functional change, only code reordering and self-encapsulation.

The series adds a macro check in thermal_core.h in order to warn in
case a driver is including the thermal core private headers.

Then the thermal zone device structure is moved from the exported
thermal.h header to the thermal_core.h

Daniel Lezcano (3):
  thermal/core: Hardening the self-encapsulation
  thermal/core: Reorder the headers inclusion
  thermal/core: Move the thermal zone structure to the private core
    header

 drivers/thermal/gov_bang_bang.c       |  1 +
 drivers/thermal/gov_fair_share.c      |  1 +
 drivers/thermal/gov_power_allocator.c |  7 ++-
 drivers/thermal/gov_step_wise.c       |  1 +
 drivers/thermal/gov_user_space.c      |  1 +
 drivers/thermal/thermal_acpi.c        |  1 +
 drivers/thermal/thermal_core.c        |  7 ++-
 drivers/thermal/thermal_core.h        | 79 +++++++++++++++++++++++++++
 drivers/thermal/thermal_helpers.c     |  1 +
 drivers/thermal/thermal_hwmon.c       |  1 +
 drivers/thermal/thermal_netlink.c     |  1 +
 drivers/thermal/thermal_of.c          |  1 +
 drivers/thermal/thermal_sysfs.c       |  1 +
 drivers/thermal/thermal_trip.c        |  1 +
 include/linux/thermal.h               | 75 -------------------------
 15 files changed, 98 insertions(+), 81 deletions(-)

-- 
2.34.1


             reply	other threads:[~2023-04-18  8:31 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-18  8:30 Daniel Lezcano [this message]
2023-04-18  8:30 ` [PATCH v1 1/3] thermal/core: Hardening the self-encapsulation Daniel Lezcano
2023-04-18  8:30 ` [PATCH v1 2/3] thermal/core: Reorder the headers inclusion Daniel Lezcano
2023-04-18  8:30 ` [PATCH v1 3/3] thermal/core: Move the thermal zone structure to the private core header 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=20230418083055.3611721-1-daniel.lezcano@linaro.org \
    --to=daniel.lezcano@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=rafael@kernel.org \
    --cc=rui.zhang@intel.com \
    --cc=thierry.reding@gmail.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

all inboxes | Powered by JetHome®