From: Wolfram Sang <wsa+renesas@sang-engineering.com>
To: Guenter Roeck <linux@roeck-us.net>
Cc: Hardware Monitoring <linux-hwmon@vger.kernel.org>
Subject: Re: [RFC/RFT PATCH v2] hwmon: (lm75) Hide register size differences in regmap access functions
Date: Wed, 18 Dec 2024 17:25:26 +0100 [thread overview]
Message-ID: <Z2L3dhneuMi9ckUe@ninjato> (raw)
In-Reply-To: <bfb3ba78-206d-4f28-a57d-c25e7d90361d@roeck-us.net>
[-- Attachment #1: Type: text/plain, Size: 555 bytes --]
> Ah yes, 'client' can be passed as bus context, and isn't used elsewhere.
> The access functions need lm75_data, but they can get the pointer to it
> from drvdata.
Yup, that's exactly what I did.
> Maybe that should be part of this patch. I assume you'll take it over - do you
> want to make that change or should I send another version ? Handling it in a
> separate patch is fine with me as well if you prefer to do that.
Since I already have that patch on top, I suggest to keep it
incremental. Also easier to debug if something goes wrong etc...
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2024-12-18 16:25 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-18 15:04 [RFC/RFT PATCH v2] hwmon: (lm75) Hide register size differences in regmap access functions Guenter Roeck
2024-12-18 16:07 ` Wolfram Sang
2024-12-18 16:21 ` Guenter Roeck
2024-12-18 16:25 ` Wolfram Sang [this message]
2024-12-18 16:36 ` Guenter Roeck
2024-12-18 16:41 ` Guenter Roeck
2024-12-18 17:39 ` Wolfram Sang
2024-12-18 17:53 ` Guenter Roeck
2024-12-20 6:21 ` 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=Z2L3dhneuMi9ckUe@ninjato \
--to=wsa+renesas@sang-engineering.com \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux@roeck-us.net \
/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.