From: Krzysztof Kozlowski <krzk@kernel.org>
To: Diogo Ivo <diogo.ivo@siemens.com>,
"Rafael J. Wysocki" <rafael@kernel.org>,
Len Brown <lenb@kernel.org>,
Wim Van Sebroeck <wim@linux-watchdog.org>,
Guenter Roeck <linux@roeck-us.net>
Cc: linux-kernel@vger.kernel.org, linux-acpi@vger.kernel.org,
linux-watchdog@vger.kernel.org, jan.kiszka@siemens.com,
benedikt.niedermayr@siemens.com
Subject: Re: [PATCH] watchdog: Add driver for Intel OC WDT
Date: Wed, 12 Mar 2025 09:50:45 +0100 [thread overview]
Message-ID: <bd411390-25bd-417e-9caa-aa4a45ad9161@kernel.org> (raw)
In-Reply-To: <20250311-ivo-intel_oc_wdt-v1-1-fd470460d9f5@siemens.com>
On 11/03/2025 14:18, Diogo Ivo wrote:
> diff --git a/drivers/watchdog/Kconfig b/drivers/watchdog/Kconfig
> index f81705f8539aa0b12d156a86aae521aa40b4527d..16e6df441bb344c0f91b40bd76b6322ad3016e72 100644
> --- a/drivers/watchdog/Kconfig
> +++ b/drivers/watchdog/Kconfig
> @@ -1350,6 +1350,17 @@ config INTEL_MID_WATCHDOG
>
> To compile this driver as a module, choose M here.
>
> +config INTEL_OC_WATCHDOG
> + tristate "Intel OC Watchdog"
> + depends on X86 && ACPI
Why can't this be compile tested?
...
> +static const struct acpi_device_id intel_oc_wdt_match[] = {
> + { "INT3F0D" },
> + { "INTC1099" },
> + { },
> +};
> +MODULE_DEVICE_TABLE(acpi, intel_oc_wdt_match);
> +
> +static struct platform_driver intel_oc_wdt_platform_driver = {
> + .driver = {
> + .name = DRV_NAME,
> + .acpi_match_table = ACPI_PTR(intel_oc_wdt_match),
Drop ACPI_PTR, causes warnigns and is not really beneficial.
> + },
> + .probe = intel_oc_wdt_probe,
> +};
> +
> +module_platform_driver(intel_oc_wdt_platform_driver);
> +
> +MODULE_AUTHOR("Diogo Ivo <diogo.ivo@siemens.com>");
> +MODULE_LICENSE("GPL");
> +MODULE_DESCRIPTION("Intel OC Watchdog driver");
> +MODULE_ALIAS("platform:" DRV_NAME);
Drop alias, you have match table.
Best regards,
Krzysztof
next prev parent reply other threads:[~2025-03-12 8:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-11 13:18 [PATCH] watchdog: Add driver for Intel OC WDT Diogo Ivo
2025-03-11 14:10 ` Guenter Roeck
2025-03-11 14:59 ` Diogo Ivo
2025-03-11 16:06 ` Guenter Roeck
2025-03-11 16:49 ` Diogo Ivo
2025-03-12 8:50 ` Krzysztof Kozlowski [this message]
2025-03-12 15:38 ` Diogo Ivo
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=bd411390-25bd-417e-9caa-aa4a45ad9161@kernel.org \
--to=krzk@kernel.org \
--cc=benedikt.niedermayr@siemens.com \
--cc=diogo.ivo@siemens.com \
--cc=jan.kiszka@siemens.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-watchdog@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=rafael@kernel.org \
--cc=wim@linux-watchdog.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