All of lore.kernel.org
 help / color / mirror / Atom feed
From: Denis Pauk <pauk.denis@gmail.com>
To: sebastian.arnhold@posteo.de
Cc: ahmad@khalifa.ws, chunkeey@gmail.com,
	linux-hwmon@vger.kernel.org, linux@roeck-us.net,
	jdelvare@suse.com, jeroen@beerstra.org, sst@poczta.fm
Subject: Re: [PATCH RFT] hwmon: (nct6755) Add support for NCT6799D
Date: Sat, 7 Jan 2023 20:50:36 +0200	[thread overview]
Message-ID: <20230107205036.7aff1267@gmail.com> (raw)
In-Reply-To: <20230107183739.2101-1-pauk.denis@gmail.com>

On Sat,  7 Jan 2023 20:37:39 +0200
Denis Pauk <pauk.denis@gmail.com> wrote:

Of course, if Ahmad does not have any objections.

I have cleaned up patch and reused same method for both types of boards and
have added more boards.

> Hi,
> 
> Jeroen Beerstra and Slawomir Stepien have tested ASUS boards with nct6799d
> chip.
> 
> I have merged your patch with rewrited wmi access patch and attached to
> https://bugzilla.kernel.org/show_bug.cgi?id=204807#c281
> 
> I will send patches with updated wmi code after feedbacks from 204807
> receipients.
> 
> Best regards,
>              Denis.


  reply	other threads:[~2023-01-07 18:50 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20221228135744.281752-1-linux () roeck-us ! net>
2022-12-30 17:32 ` [PATCH RFT] hwmon: (nct6755) Add support for NCT6799D Christian Lamparter
2022-12-30 17:50   ` Guenter Roeck
2022-12-30 20:34     ` Christian Lamparter
2022-12-30 21:48       ` Guenter Roeck
2022-12-30 22:13         ` Sebastian Arnhold
2022-12-30 22:46           ` Guenter Roeck
2022-12-30 22:58           ` Christian Lamparter
2022-12-31 23:42             ` Sebastian Arnhold
2023-01-04  3:41               ` Guenter Roeck
2023-01-05 12:46                 ` Sebastian Arnhold
2023-01-07 18:37                   ` Denis Pauk
2023-01-07 18:50                     ` Denis Pauk [this message]
2022-12-28 13:57 Guenter Roeck
2023-05-11 21:02 ` Denis Pauk

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=20230107205036.7aff1267@gmail.com \
    --to=pauk.denis@gmail.com \
    --cc=ahmad@khalifa.ws \
    --cc=chunkeey@gmail.com \
    --cc=jdelvare@suse.com \
    --cc=jeroen@beerstra.org \
    --cc=linux-hwmon@vger.kernel.org \
    --cc=linux@roeck-us.net \
    --cc=sebastian.arnhold@posteo.de \
    --cc=sst@poczta.fm \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.