From: "Danilo Krummrich" <dakr@kernel.org>
To: "Guenter Roeck" <linux@roeck-us.net>
Cc: <gregkh@linuxfoundation.org>, <rafael@kernel.org>,
<hanguidong02@gmail.com>, <ysato@users.sourceforge.jp>,
<dalias@libc.org>, <glaubitz@physik.fu-berlin.de>,
<abelvesa@kernel.org>, <srini@kernel.org>,
<s.nawrocki@samsung.com>, <nuno.sa@analog.com>,
<driver-core@lists.linux.dev>, <linux-kernel@vger.kernel.org>,
<imx@lists.linux.dev>, <linux-hwmon@vger.kernel.org>,
<linux-arm-msm@vger.kernel.org>, <linux-sound@vger.kernel.org>,
<linux-sh@vger.kernel.org>, "Guenter Roeck" <groeck7@gmail.com>
Subject: Re: [PATCH v2 3/4] hwmon: axi-fan: don't use driver_override as IRQ name
Date: Tue, 03 Mar 2026 17:25:07 +0100 [thread overview]
Message-ID: <DGTACERFTTCV.29XON9ZLYAEQL@kernel.org> (raw)
In-Reply-To: <b46c5757-b67d-4949-b8d8-54b799464b5d@roeck-us.net>
On Tue Mar 3, 2026 at 5:23 PM CET, Guenter Roeck wrote:
> On Tue, Mar 03, 2026 at 12:53:20PM +0100, Danilo Krummrich wrote:
>> Do not use driver_override as IRQ name, as it is not guaranteed to point
>> to a valid string; use NULL instead (which makes the devm IRQ helpers
>> use dev_name()).
>>
>> Fixes: 8412b410fa5e ("hwmon: Support ADI Fan Control IP")
>> Signed-off-by: Danilo Krummrich <dakr@kernel.org>
>> Reviewed-by: Nuno Sá <nuno.sa@analog.com>
>
> Applied.
I need this patch in the driver-core tree, otherwise I can't land patch 4 of
this series [1]. :(
Any chance you can drop it from your tree?
[1] https://lore.kernel.org/driver-core/20260303115720.48783-5-dakr@kernel.org/
next prev parent reply other threads:[~2026-03-03 16:25 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-03 11:53 [PATCH v2 0/4] driver core: generalize driver_override infrastructure Danilo Krummrich
2026-03-03 11:53 ` [PATCH v2 1/4] driver core: generalize driver_override in struct device Danilo Krummrich
2026-03-03 21:01 ` Frank Li
2026-03-04 2:27 ` Gui-Dong Han
2026-03-03 11:53 ` [PATCH v2 2/4] docs: driver-model: document driver_override Danilo Krummrich
2026-03-03 21:01 ` Frank Li
2026-03-03 11:53 ` [PATCH v2 3/4] hwmon: axi-fan: don't use driver_override as IRQ name Danilo Krummrich
2026-03-03 14:53 ` Nuno Sá
2026-03-03 16:23 ` Guenter Roeck
2026-03-03 16:25 ` Danilo Krummrich [this message]
2026-03-03 16:57 ` Guenter Roeck
2026-03-03 19:18 ` Danilo Krummrich
2026-03-03 21:01 ` Frank Li
2026-03-03 11:53 ` [PATCH v2 4/4] driver core: platform: use generic driver_override infrastructure Danilo Krummrich
2026-03-03 21:01 ` Frank Li
2026-03-05 12:42 ` Danilo Krummrich
2026-03-12 20:15 ` Danilo Krummrich
2026-03-16 23:56 ` Danilo Krummrich
2026-03-17 5:06 ` Greg KH
2026-03-17 8:36 ` Geert Uytterhoeven
2026-03-03 13:03 ` [PATCH v2 0/4] driver core: generalize " Gui-Dong Han
2026-03-12 15:21 ` Greg KH
2026-03-17 20:17 ` Danilo Krummrich
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=DGTACERFTTCV.29XON9ZLYAEQL@kernel.org \
--to=dakr@kernel.org \
--cc=abelvesa@kernel.org \
--cc=dalias@libc.org \
--cc=driver-core@lists.linux.dev \
--cc=glaubitz@physik.fu-berlin.de \
--cc=gregkh@linuxfoundation.org \
--cc=groeck7@gmail.com \
--cc=hanguidong02@gmail.com \
--cc=imx@lists.linux.dev \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sh@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=nuno.sa@analog.com \
--cc=rafael@kernel.org \
--cc=s.nawrocki@samsung.com \
--cc=srini@kernel.org \
--cc=ysato@users.sourceforge.jp \
/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.