From: Guenter Roeck <linux@roeck-us.net>
To: "Limonciello, Mario" <Mario.Limonciello@amd.com>,
Wim Van Sebroeck <wim@linux-watchdog.org>,
"open list:WATCHDOG DEVICE DRIVERS"
<linux-watchdog@vger.kernel.org>,
open list <linux-kernel@vger.kernel.org>
Cc: "ionut_n2001@yahoo.com" <ionut_n2001@yahoo.com>
Subject: Re: [PATCH] Watchdog: sp5100_tco: Lower verbosity of disabled watchdog hardware
Date: Mon, 9 May 2022 16:15:22 -0700 [thread overview]
Message-ID: <8a48ba53-7182-10fa-72cd-fbcee0e4369a@roeck-us.net> (raw)
In-Reply-To: <BL1PR12MB51578AC7D4CCBFBCD1DF19E4E2C69@BL1PR12MB5157.namprd12.prod.outlook.com>
On 5/9/22 16:10, Limonciello, Mario wrote:
> [Public]
>
>
>
>> -----Original Message-----
>> From: Guenter Roeck <groeck7@gmail.com> On Behalf Of Guenter Roeck
>> Sent: Monday, May 9, 2022 17:56
>> To: Limonciello, Mario <Mario.Limonciello@amd.com>; Wim Van Sebroeck
>> <wim@linux-watchdog.org>; open list:WATCHDOG DEVICE DRIVERS <linux-
>> watchdog@vger.kernel.org>; open list <linux-kernel@vger.kernel.org>
>> Cc: ionut_n2001@yahoo.com
>> Subject: Re: [PATCH] Watchdog: sp5100_tco: Lower verbosity of disabled
>> watchdog hardware
>>
>> On 5/9/22 09:33, Mario Limonciello wrote:
>>> If watchdog hardware has been disabled, currently the kernel driver
>>> will show at err level during probe:
>>>
>>> "Watchdog hardware is disabled"
>>>
>>> This is unnecessarily verbose as there is already a -ENODEV returned.
>>> Lower the level to debug.
>>
>> Is it ? Without this message, a user may try to load the driver,
>> get an error message, and have no idea why the driver was not
>> enabled even though the hardware exists. If anything , -ENODEV
>> is less than perfect. Unfortunately there does not seem to be
>> a better error code, or at least I don't see one.
>
> If it didn't have modaliases and users only manually loaded it; I would agree
> with you. However it has MODULE_DEVICE_TABLE, so if that PCI device is around
> then the driver will load either way. That would translate into an "error message"
> on every boot if you have this module compiled and didn't manually try to load it.
>
Why don't you just blacklist the driver ?
Guenter
next prev parent reply other threads:[~2022-05-09 23:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-09 16:33 Mario Limonciello
2022-05-09 22:55 ` Guenter Roeck
2022-05-09 23:10 ` Limonciello, Mario
2022-05-09 23:15 ` Guenter Roeck [this message]
2022-05-10 0:33 ` Jerry Hoemann
2022-05-10 0:37 ` Mario Limonciello
2022-05-10 1:15 ` Guenter Roeck
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=8a48ba53-7182-10fa-72cd-fbcee0e4369a@roeck-us.net \
--to=linux@roeck-us.net \
--cc=Mario.Limonciello@amd.com \
--cc=ionut_n2001@yahoo.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-watchdog@vger.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
all inboxes | Powered by JetHome®