From: Guenter Roeck <linux@roeck-us.net>
To: Bjorn Helgaas <helgaas@kernel.org>
Cc: "Enrico Weigelt, metux IT consult" <info@metux.net>,
linux-kernel@vger.kernel.org, wim@linux-watchdog.org,
linux-watchdog@vger.kernel.org
Subject: Re: [PATCH 2/3] watchdog: iTCO_wdt: use dev_*() instead of pr_*() for logging
Date: Wed, 9 Jun 2021 16:54:46 -0700 [thread overview]
Message-ID: <20210609235446.GA2542004@roeck-us.net> (raw)
In-Reply-To: <20210609203229.GA2664456@bjorn-Precision-5520>
On Wed, Jun 09, 2021 at 03:32:29PM -0500, Bjorn Helgaas wrote:
> On Tue, Nov 17, 2020 at 04:22:13PM +0100, Enrico Weigelt, metux IT consult wrote:
> > For device log outputs, it's better to have device name / ID
> > prefixed in all messages, so use the proper dev_*() functions here.
> >
> > Explicit message on module load/unload don't seem to be really helpful
> > (we have other means to check which modules have been loaded), instead
> > just add noise to the kernel log. So, removing them.
> >
> > Signed-off-by: Enrico Weigelt, metux IT consult <info@metux.net>
>
> I like this patch a lot; thanks for doing it! It's merged upstream as
> c21172b3a73e ("watchdog: iTCO_wdt: use dev_*() instead of pr_*() for
> logging").
>
> It looks like there are a couple more pr_err() uses, so I wondered if
> they were missed or skipped intentionally:
>
> if (p->smi_res) {
> /* The TCO logic uses the TCO_EN bit in the SMI_EN register */
> if (!devm_request_region(dev, p->smi_res->start,
> resource_size(p->smi_res),
> pdev->name)) {
> pr_err("I/O address 0x%04llx already in use, device disabled\n",
> (u64)SMI_EN(p));
> return -EBUSY;
> }
> } else if (iTCO_vendorsupport ||
> turn_SMI_watchdog_clear_off >= p->iTCO_version) {
> pr_err("SMI I/O resource is missing\n");
> return -ENODEV;
> }
>
The above came in with a recent commit. I suspect they simply got lost,
and they should be converted as well.
Guenter
next prev parent reply other threads:[~2021-06-09 23:56 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-17 15:22 [PATCH 1/3] watchdog: iTCO_wdt: use module_platform_device() macro Enrico Weigelt, metux IT consult
2020-11-17 15:22 ` [PATCH 2/3] watchdog: iTCO_wdt: use dev_*() instead of pr_*() for logging Enrico Weigelt, metux IT consult
2020-11-30 22:08 ` Guenter Roeck
2021-06-09 20:32 ` Bjorn Helgaas
2021-06-09 23:54 ` Guenter Roeck [this message]
2021-06-14 17:55 ` Enrico Weigelt, metux IT consult
2021-06-15 14:51 ` Bjorn Helgaas
2020-11-17 15:22 ` [PATCH 3/3] watchdog: iTCO_wdt: use pm_ptr() Enrico Weigelt, metux IT consult
2020-11-30 22:17 ` Guenter Roeck
2020-11-30 22:06 ` [PATCH 1/3] watchdog: iTCO_wdt: use module_platform_device() macro 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=20210609235446.GA2542004@roeck-us.net \
--to=linux@roeck-us.net \
--cc=helgaas@kernel.org \
--cc=info@metux.net \
--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