mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Guenter Roeck <linux@roeck-us.net>
To: Armin Wolf <W_Armin@gmx.de>, james@equiv.tech
Cc: jdelvare@suse.com, linux-hwmon@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [RFC 0/1] hwmon: (hp-wmi-sensors) Support autoloading
Date: Mon, 18 Mar 2024 16:04:12 -0700	[thread overview]
Message-ID: <d167915c-e55e-4c2b-b7dc-6f4bda2f3a34@roeck-us.net> (raw)
In-Reply-To: <20240318215732.322798-1-W_Armin@gmx.de>

On 3/18/24 14:57, Armin Wolf wrote:
> Currently, the hp-wmi-sensors driver needs to be loaded manually
> on supported machines. This however is unnecessary since the WMI
> id table can be used to support autoloading.
> 
> However the driver might conflict with the hp-wmi driver since both
> seem to use the same WMI GUID for registering notify handler.
> 

I have no idea how this is supposed to be handled.
wmi_install_notify_handler() is marked as deprecated,
suggesting that the entire driver structure may be outdated.

> I am thus submitting this patch as an RFC for now.
> 

.... and, given the above, I have no idea what to do with it, sorry.

Guenter


  parent reply	other threads:[~2024-03-18 23:04 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-18 21:57 Armin Wolf
2024-03-18 21:57 ` [RFC PATCH 1/1] hwmon: (hp-wmi-sensors) Add missing MODULE_DEVICE_TABLE() Armin Wolf
2024-03-18 23:04 ` Guenter Roeck [this message]
2024-03-19  5:47 ` [RFC 0/1] hwmon: (hp-wmi-sensors) Support autoloading James Seo
2024-03-19 13:00   ` Armin Wolf
2024-03-20  0:40     ` James Seo
2024-03-20 15:13       ` Armin Wolf
2024-03-20 20:11         ` James Seo
2024-03-20 22:09           ` Armin Wolf
2024-03-21  6:33             ` James Seo

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=d167915c-e55e-4c2b-b7dc-6f4bda2f3a34@roeck-us.net \
    --to=linux@roeck-us.net \
    --cc=W_Armin@gmx.de \
    --cc=james@equiv.tech \
    --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®