mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Randy Dunlap <rdunlap@infradead.org>
To: Yuxi Wang <Yuxi.Wang@monolithicpower.com>,
	linux@roeck-us.net, corbet@lwn.net, robh@kernel.org,
	krzk+dt@kernel.org, conor+dt@kernel.org
Cc: wyx137120466@gmail.com, linux-hwmon@vger.kernel.org,
	linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
	devicetree@vger.kernel.org
Subject: Re: [PATCH 2/2] hwmon: add mp5926 driver
Date: Sun, 7 Dec 2025 23:49:35 -0800	[thread overview]
Message-ID: <2adbb279-3939-44c3-9849-ecbc33b2613d@infradead.org> (raw)
In-Reply-To: <20251208071659.1157-3-Yuxi.Wang@monolithicpower.com>



On 12/7/25 11:16 PM, Yuxi Wang wrote:
> diff --git a/drivers/hwmon/pmbus/Kconfig b/drivers/hwmon/pmbus/Kconfig
> index f3fb94cebf1a..0a6699fa976a 100644
> --- a/drivers/hwmon/pmbus/Kconfig
> +++ b/drivers/hwmon/pmbus/Kconfig
> @@ -472,6 +472,15 @@ config SENSORS_MP5920
>  	  This driver can also be built as a module. If so, the module will
>  	  be called mp5920.
>  
> +config SENSORS_MP5926
> +	tristate "MPS MP5926"
> +	help
> +	  If you say yes here you get hardware monitoring support for Monolithic
> +	  MP5926.
> +
> +	  This driver can also be built as a module. If so, the module will
> +	  be called MP5926.

	            mp5926.
(don't want to confuse anyone)

-- 
~Randy


      parent reply	other threads:[~2025-12-08  7:49 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-08  7:16 [PATCH 0/2] hwmon: Add support for MPS mp5926 chip Yuxi Wang
2025-12-08  7:16 ` [PATCH 1/2] dt-bindings: hwmon: Add MPS mp5926 Yuxi Wang
2025-12-08  7:23   ` Krzysztof Kozlowski
2025-12-08  7:16 ` [PATCH 2/2] hwmon: add mp5926 driver Yuxi Wang
2025-12-08  7:39   ` Guenter Roeck
2025-12-08  7:49   ` Randy Dunlap [this message]

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=2adbb279-3939-44c3-9849-ecbc33b2613d@infradead.org \
    --to=rdunlap@infradead.org \
    --cc=Yuxi.Wang@monolithicpower.com \
    --cc=conor+dt@kernel.org \
    --cc=corbet@lwn.net \
    --cc=devicetree@vger.kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-hwmon@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@roeck-us.net \
    --cc=robh@kernel.org \
    --cc=wyx137120466@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®