Linux Hardware Monitor development
 help / color / mirror / Atom feed
From: Guenter Roeck <linux@roeck-us.net>
To: Wolfram Sang <wsa+renesas@sang-engineering.com>
Cc: linux-renesas-soc@vger.kernel.org,
	Jean Delvare <jdelvare@suse.com>,
	linux-hwmon@vger.kernel.org
Subject: Re: [RFC PATCH 1/5] hwmon: (lm75) simplify lm75_write_config()
Date: Fri, 20 Dec 2024 06:56:46 -0800	[thread overview]
Message-ID: <a2c4bb48-8ed8-4225-82dc-232cc0708958@roeck-us.net> (raw)
In-Reply-To: <20241219225522.3490-8-wsa+renesas@sang-engineering.com>

On Thu, Dec 19, 2024 at 11:55:23PM +0100, Wolfram Sang wrote:
> After previous refactoring, it is now possible to make
> lm75_write_config() a simple inline function.
> 
> Signed-off-by: Wolfram Sang <wsa+renesas@sang-engineering.com>
> Reviewed-by: Geert Uytterhoeven <geert+renesas@glider.be>

Applied.

Thanks,
Gueter

  parent reply	other threads:[~2024-12-20 14:56 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-19 22:55 [RFC PATCH 0/5] hwmon: (lm75) add I3C support Wolfram Sang
2024-12-19 22:55 ` [RFC PATCH 1/5] hwmon: (lm75) simplify lm75_write_config() Wolfram Sang
2024-12-20  8:48   ` Geert Uytterhoeven
2024-12-20 14:56   ` Guenter Roeck [this message]
2024-12-19 22:55 ` [RFC PATCH 2/5] hwmon: (lm75) simplify regulator handling Wolfram Sang
2024-12-20  8:50   ` Geert Uytterhoeven
2024-12-20 14:57   ` Guenter Roeck
2024-12-19 22:55 ` [RFC PATCH 3/5] hwmon: (lm75) Remove superfluous 'client' member from private struct Wolfram Sang
2024-12-20 14:57   ` Guenter Roeck
2024-12-19 22:55 ` [RFC PATCH 4/5] hwmon: (lm75) separate probe into common and I2C parts Wolfram Sang
2024-12-20 14:58   ` Guenter Roeck
2024-12-19 22:55 ` [RFC PATCH 5/5] hwmon: (lm75) add I3C support for P3T1755 Wolfram Sang
2024-12-20  6:10   ` Guenter Roeck
2024-12-20  8:20     ` Wolfram Sang

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=a2c4bb48-8ed8-4225-82dc-232cc0708958@roeck-us.net \
    --to=linux@roeck-us.net \
    --cc=jdelvare@suse.com \
    --cc=linux-hwmon@vger.kernel.org \
    --cc=linux-renesas-soc@vger.kernel.org \
    --cc=wsa+renesas@sang-engineering.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