linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Guenter Roeck <linux@roeck-us.net>
To: Daniel Dawson <danielcdawson@gmail.com>
Cc: Jean Delvare <jdelvare@suse.com>,
	linux-hwmon@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Add another customer ID for NCT6683D sensor chip on some ASRock boards.
Date: Thu, 23 Sep 2021 19:02:50 -0700	[thread overview]
Message-ID: <20210924020250.GA3031547@roeck-us.net> (raw)
In-Reply-To: <20210921165859.48714-1-danielcdawson@gmail.com>

On Tue, Sep 21, 2021 at 09:58:59AM -0700, Daniel Dawson wrote:
> This value was found on a Z370M Pro4 rev. 1.01, with an
> NCT6683D-T chip.
> 
> Signed-off-by: Daniel Dawson <danielcdawson@gmail.com>

Applied. In the future, please indicate the subsystem and the affected
driver in the subject line. See other patches for examples.

Thanks,
Guenter

> ---
>  drivers/hwmon/nct6683.c | 3 +++
>  1 file changed, 3 insertions(+)
> 
> diff --git a/drivers/hwmon/nct6683.c b/drivers/hwmon/nct6683.c
> index 35f8635dc7f3..6a9f420e7d32 100644
> --- a/drivers/hwmon/nct6683.c
> +++ b/drivers/hwmon/nct6683.c
> @@ -174,6 +174,7 @@ superio_exit(int ioreg)
>  #define NCT6683_CUSTOMER_ID_MITAC	0xa0e
>  #define NCT6683_CUSTOMER_ID_MSI		0x201
>  #define NCT6683_CUSTOMER_ID_ASROCK		0xe2c
> +#define NCT6683_CUSTOMER_ID_ASROCK2	0xe1b
>  
>  #define NCT6683_REG_BUILD_YEAR		0x604
>  #define NCT6683_REG_BUILD_MONTH		0x605
> @@ -1221,6 +1222,8 @@ static int nct6683_probe(struct platform_device *pdev)
>  		break;
>  	case NCT6683_CUSTOMER_ID_ASROCK:
>  		break;
> +	case NCT6683_CUSTOMER_ID_ASROCK2:
> +		break;
>  	default:
>  		if (!force)
>  			return -ENODEV;

      reply	other threads:[~2021-09-24  2:02 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-21 16:58 [PATCH] Add another customer ID for NCT6683D sensor chip on some ASRock boards Daniel Dawson
2021-09-24  2:02 ` Guenter Roeck [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=20210924020250.GA3031547@roeck-us.net \
    --to=linux@roeck-us.net \
    --cc=danielcdawson@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;
as well as URLs for NNTP newsgroup(s).