From: Guenter Roeck <linux@roeck-us.net>
To: Javier Carrasco <javier.carrasco.cruz@gmail.com>
Cc: Jean Delvare <jdelvare@suse.com>,
linux-kernel@vger.kernel.org, linux-hwmon@vger.kernel.org
Subject: Re: [PATCH 1/2] MAINTAINERS: Drop IIO from the title of the Chipcap 2 hwmon driver
Date: Fri, 22 Nov 2024 09:47:44 -0800 [thread overview]
Message-ID: <bd3f8926-4e9b-4323-9cf2-8f2e9ca86298@roeck-us.net> (raw)
In-Reply-To: <20241121-chipcap_no_iio-v1-1-6c157848a36f@gmail.com>
On Thu, Nov 21, 2024 at 10:44:55PM +0100, Javier Carrasco wrote:
> The Chipcap 2 driver belongs to hwmon, and not to iio. When at it,
> drop the sensor type description, as that is documented elsewhere.
>
> Signed-off-by: Javier Carrasco <javier.carrasco.cruz@gmail.com>
> ---
> MAINTAINERS | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/MAINTAINERS b/MAINTAINERS
> index 20df6282d1d2..91936a9ba56f 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -1226,7 +1226,7 @@ S: Maintained
> F: Documentation/devicetree/bindings/rtc/amlogic,a4-rtc.yaml
> F: drivers/rtc/rtc-amlogic-a4.c
>
> -AMPHENOL CHIPCAP 2 HUMIDITY-TEMPERATURE IIO DRIVER
> +AMPHENOL CHIPCAP 2 DRIVER
I am not entirely sure I understand why you want to have
"HUMIDITY-TEMPERATURE" dropped, but then I figured that
you are the driver maintainer and that it should be your call.
Applied.
Guenter
next prev parent reply other threads:[~2024-11-22 17:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-21 21:44 [PATCH 0/2] hwmon: (chipcap2) Drop IIO in MAINTAINERS and simplify with guard() Javier Carrasco
2024-11-21 21:44 ` [PATCH 1/2] MAINTAINERS: Drop IIO from the title of the Chipcap 2 hwmon driver Javier Carrasco
2024-11-22 17:47 ` Guenter Roeck [this message]
2024-11-21 21:44 ` [PATCH 2/2] hwmon: (chipcap2) Switch to guard() for mutext handling Javier Carrasco
2024-11-22 14:45 ` Markus Elfring
2024-11-22 17:48 ` 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=bd3f8926-4e9b-4323-9cf2-8f2e9ca86298@roeck-us.net \
--to=linux@roeck-us.net \
--cc=javier.carrasco.cruz@gmail.com \
--cc=jdelvare@suse.com \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/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®