mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: Guenter Roeck <linux@roeck-us.net>
Cc: Jean Delvare <jdelvare@suse.com>,
	linux-hwmon@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/5] hwmon: Update single register drivers to use maple tree register cache
Date: Sat, 10 Jun 2023 15:24:25 +0100	[thread overview]
Message-ID: <da6696d1-7b3f-4366-a0a4-e2f7bafe8cbf@sirena.org.uk> (raw)
In-Reply-To: <e2c965e9-3bcb-5857-087a-9e457040ab88@roeck-us.net>

[-- Attachment #1: Type: text/plain, Size: 554 bytes --]

On Sat, Jun 10, 2023 at 07:15:48AM -0700, Guenter Roeck wrote:
> On 6/10/23 06:59, Mark Brown wrote:
> > A number of hwmon drivers only support single register I/O and therefore
> > gain no benefit from using the more modern maple tree register cache
> > over the rbtree cache, convert them to maple tree.

> "gain no benefit from using the more modern maple tree register cache
> over the rbtree cache, convert them to maple tree."

> Is that really what you wanted to say ?

Sorry, other way around - gain no benefit from using rbtree over maple
tree.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

  reply	other threads:[~2023-06-10 14:24 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-10 13:59 Mark Brown
2023-06-10 13:59 ` [PATCH 1/5] hwmon: (lm75) Use " Mark Brown
2023-06-10 13:59 ` [PATCH 2/5] hwmon: (lm95245) " Mark Brown
2023-06-10 13:59 ` [PATCH 3/5] hwmon: (tmp102) " Mark Brown
2023-06-10 13:59 ` [PATCH 4/5] hwmon: (tmp108) " Mark Brown
2023-06-10 13:59 ` [PATCH 5/5] hwmon: (tmp464) " Mark Brown
2023-06-10 14:15 ` [PATCH 0/5] hwmon: Update single register drivers to use " Guenter Roeck
2023-06-10 14:24   ` Mark Brown [this message]
2023-06-10 14:36     ` Guenter Roeck

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=da6696d1-7b3f-4366-a0a4-e2f7bafe8cbf@sirena.org.uk \
    --to=broonie@kernel.org \
    --cc=jdelvare@suse.com \
    --cc=linux-hwmon@vger.kernel.org \
    --cc=linux-kernel@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 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®