All of lore.kernel.org
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzk@kernel.org>
To: Cryolitia PukNgae <cryolitia@gmail.com>,
	Jean Delvare <jdelvare@suse.com>,
	Guenter Roeck <linux@roeck-us.net>,
	Jonathan Corbet <corbet@lwn.net>
Cc: linux-kernel@vger.kernel.org, linux-hwmon@vger.kernel.org,
	linux-doc@vger.kernel.org,
	"Celeste Liu" <CoelacanthusHex@gmail.com>,
	"Marcin Strągowski" <marcin@stragowski.com>
Subject: Re: [PATCH v2 1/2] hwmon: add GPD devices sensor driver
Date: Wed, 17 Jul 2024 09:04:17 +0200	[thread overview]
Message-ID: <d2b4beee-5eb6-4976-844a-76981a604067@kernel.org> (raw)
In-Reply-To: <fd9423c0-8c2b-4aef-9d76-cb7def3e2344@gmail.com>

On 17/07/2024 09:01, Cryolitia PukNgae wrote:
> 
> On 2024/7/17 03:28, Krzysztof Kozlowski wrote:
>> Why would you add here untested models?
> The manufacturer GPD  sent me these quirks and reg addresses, and they 
> used them to write their Windows user space driver. They are unlikely to 
> have problems. It was fully tested by several people on WIn Max 2 2023 
> and Win 4, and there's only little address difference with other model.

Then just skip this testing checks.

Best regards,
Krzysztof


  reply	other threads:[~2024-07-17  7:04 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-16 16:58 [PATCH v2 0/2] hwmon: add GPD devices sensor driver Cryolitia PukNgae
2024-07-16 16:58 ` Cryolitia PukNgae via B4 Relay
2024-07-16 16:58 ` [PATCH v2 1/2] " Cryolitia PukNgae
2024-07-16 16:58   ` Cryolitia PukNgae via B4 Relay
2024-07-16 18:04   ` Guenter Roeck
2024-07-17  7:03     ` Cryolitia PukNgae
2024-07-16 19:28   ` Krzysztof Kozlowski
2024-07-17  7:01     ` Cryolitia PukNgae
2024-07-17  7:04       ` Krzysztof Kozlowski [this message]
2024-07-16 16:58 ` [PATCH v2 2/2] hwmon: document: add gpd-fan Cryolitia PukNgae
2024-07-16 16:58   ` Cryolitia PukNgae via B4 Relay
2024-07-16 21:20   ` Randy Dunlap

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=d2b4beee-5eb6-4976-844a-76981a604067@kernel.org \
    --to=krzk@kernel.org \
    --cc=CoelacanthusHex@gmail.com \
    --cc=corbet@lwn.net \
    --cc=cryolitia@gmail.com \
    --cc=jdelvare@suse.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-hwmon@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@roeck-us.net \
    --cc=marcin@stragowski.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 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.