From: Guenter Roeck <linux@roeck-us.net>
To: "Reiner Pröls" <reiner.proels@gmail.com>
Cc: linux-hwmon@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] hwmon: nct6683 Add support for ASRock Z890 Pro-A
Date: Wed, 20 May 2026 12:54:41 -0700 [thread overview]
Message-ID: <7ec1cd4a-c094-42a2-ba60-e6cc7d82e7e2@roeck-us.net> (raw)
In-Reply-To: <4eee938d-e4ca-427d-a161-aa9ef737af3c@gmail.com>
On Wed, May 20, 2026 at 09:16:37PM +0200, Reiner Pröls wrote:
> From ac010d19f5ba1e44a0ddb83cc570f18ca3348015 Mon Sep 17 00:00:00 2001
> From: =?UTF-8?q?Reiner=20Pr=C3=B6ls?= <Reiner.Pröls@gmail.com>
> Date: Wed, 20 May 2026 20:59:57 +0200
> Subject: [PATCH] Add support for ASRock Z890 Pro-A mainboard
Subject should be
"hwmon: (nct6683) Add support for ASRock Z890 Pro-A"
or similar. Actually, your outer subject comes close.
> MIME-Version: 1.0
> Content-Type: text/plain; charset=UTF-8
> Content-Transfer-Encoding: 8bit
>
Description goes here. Look into the driver log for examples.
Also, it looks like you embedded your patch in another patch
with a different subject. That probably triggers:
WARNING: From:/Signed-off-by: email address mismatch: 'From: "Reiner Pröls" <Reiner.Pröls@gmail.com>' != 'Signed-off-by: Reiner Pröls <Reiner.Pröls@gmail.com>'
Also, when I try to apply the patch, I get "patch is empty".
Please fix this up.
> Signed-off-by: Reiner Pröls <Reiner.Pröls@gmail.com>
> ---
> drivers/hwmon/nct6683.c | 5 ++++-
> 1 file changed, 4 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/hwmon/nct6683.c b/drivers/hwmon/nct6683.c
> index 0581770380cc..1b9092f48c7d 100644
> --- a/drivers/hwmon/nct6683.c
> +++ b/drivers/hwmon/nct6683.c
> @@ -177,12 +177,13 @@ superio_exit(int ioreg)
> #define NCT6683_CUSTOMER_ID_MSI3 0x207
> #define NCT6683_CUSTOMER_ID_MSI4 0x20d
> #define NCT6683_CUSTOMER_ID_AMD 0x162b
> -#define NCT6683_CUSTOMER_ID_ASROCK 0xe2c
> +#define NCT6683_CUSTOMER_ID_ASROCK 0xe2c
> #define NCT6683_CUSTOMER_ID_ASROCK2 0xe1b
> #define NCT6683_CUSTOMER_ID_ASROCK3 0x1631
> #define NCT6683_CUSTOMER_ID_ASROCK4 0x163e
> #define NCT6683_CUSTOMER_ID_ASROCK5 0x1621
> #define NCT6683_CUSTOMER_ID_ASROCK6 0x1633
> +#define NCT6683_CUSTOMER_ID_ASROCK7 0x163d // Z890 Pro-A
No C++ comments in this file, please.
>
> #define NCT6683_REG_BUILD_YEAR 0x604
> #define NCT6683_REG_BUILD_MONTH 0x605
> @@ -1248,6 +1249,8 @@ static int nct6683_probe(struct platform_device *pdev)
> break;
> case NCT6683_CUSTOMER_ID_ASROCK6:
> break;
> + case NCT6683_CUSTOMER_ID_ASROCK7:
> + break;
Was this cut-and-paste ? There are no tabs, just spaces, meaning the
patch would not apply. That would also explain the duplicated headers.
Guenter
> default:
> if (!force)
> return -ENODEV;
> --
> 2.43.0
>
>
next prev parent reply other threads:[~2026-05-20 19:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-20 19:16 Reiner Pröls
2026-05-20 19:54 ` Guenter Roeck [this message]
2026-05-20 20:46 ` Reiner Pröls
2026-05-20 21:02 ` Guenter Roeck
2026-05-21 21:26 [PATCH] hwmon: (nct6683) " Reiner Pröls
2026-05-24 15:31 ` 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=7ec1cd4a-c094-42a2-ba60-e6cc7d82e7e2@roeck-us.net \
--to=linux@roeck-us.net \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=reiner.proels@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
Powered by JetHome