public inbox for linux-pm@vger.kernel.org
 help / color / mirror / Atom feed
From: "Rafael J. Wysocki" <rjw@rjwysocki.net>
To: Daniel Lezcano <daniel.lezcano@linaro.org>,
	Lukasz Luba <lukasz.luba@arm.com>
Cc: Linux PM <linux-pm@vger.kernel.org>,
	LKML <linux-kernel@vger.kernel.org>,
	Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>,
	Zhang Rui <rui.zhang@intel.com>
Subject: [PATCH v1 0/2] thermal: sysfs: Simplifications of trip point attribute callbacks
Date: Thu, 30 Nov 2023 19:27:36 +0100	[thread overview]
Message-ID: <5754079.DvuYhMxLoT@kreacher> (raw)

Hi,

These patches simplify trip point attribute callbacks in two ways.

The first patch, which is a direct replacement for

https://patchwork.kernel.org/project/linux-pm/patch/4869676.GXAFRqVoOG@kreacher/

gets rid of redundant steps from the _store() callbacks for the trip point
temperature and hysteresis and makes them use zone locking only as necessary.

The second patch eliminates zone locking from all of the _show() callbacks
for trip point temperature, hysteresis and type, because it is not needed
there.

Please refer to the individual patch changelogs for details.

Thanks!





             reply	other threads:[~2023-11-30 18:38 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-30 18:27 Rafael J. Wysocki [this message]
2023-11-30 18:35 ` [PATCH v1 1/2] thermal: sysfs: Rework the handling of trip point updates Rafael J. Wysocki
2023-11-30 18:37 ` [PATCH v1 2/2] thermal: sysfs: Eliminate unnecessary zone locking Rafael J. Wysocki
2023-11-30 19:33   ` Rafael J. Wysocki
2023-12-01  9:16   ` Daniel Lezcano
2023-12-01 11:05     ` Rafael J. Wysocki
2023-11-30 19:42 ` [PATCH v1.1 2/2] thermal: sysfs: Simplifications of trip point attribute callbacks Rafael J. Wysocki
2023-11-30 19:51   ` Rafael J. Wysocki
2023-11-30 19:53 ` [PATCH v1.1 2/2] thermal: sysfs: Eliminate unnecessary zone locking Rafael J. Wysocki

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=5754079.DvuYhMxLoT@kreacher \
    --to=rjw@rjwysocki.net \
    --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=srinivas.pandruvada@linux.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox