From: Michal Simek <monstr@monstr.eu>
To: Guenter Roeck <linux@roeck-us.net>,
Michal Simek <michal.simek@xilinx.com>,
linux-kernel@vger.kernel.org
Cc: linux-watchdog@vger.kernel.org, Wim Van Sebroeck <wim@iguana.be>
Subject: Re: [PATCH 2/2] watchdog: cadence_wdt: Show information when driver is probed
Date: Fri, 4 Aug 2017 15:56:09 +0200 [thread overview]
Message-ID: <e83dcbe3-a65f-d4d0-2922-5929eca45ea9@monstr.eu> (raw)
In-Reply-To: <6ad8cad8-e1a4-57ec-d25f-dc6b0935a6fb@roeck-us.net>
[-- Attachment #1.1: Type: text/plain, Size: 795 bytes --]
On 4.8.2017 15:47, Guenter Roeck wrote:
> On 08/04/2017 12:39 AM, Michal Simek wrote:
>> Showing message that driver is loaded is common across drivers.
>
> Across watchdog drivers, which I am always half-annoyed about.
> Is this really valuable ?
I don't think that this is debug message. We don't have hundreds of
drivers that log explodes and for systems, which I don't know, I do
normally check dmesg logs and I would expect this message to be there to
know that watchdog is enabled.
Thanks,
Michal
--
Michal Simek, Ing. (M.Eng), OpenPGP -> KeyID: FE3D1F91
w: www.monstr.eu p: +42-0-721842854
Maintainer of Linux kernel - Xilinx Microblaze
Maintainer of Linux kernel - Xilinx Zynq ARM and ZynqMP ARM64 SoCs
U-Boot custodian - Xilinx Microblaze/Zynq/ZynqMP SoCs
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2017-08-04 13:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-04 7:39 [PATCH 1/2] watchdog: cadence_wdt: Enable access to module parameters Michal Simek
2017-08-04 7:39 ` [PATCH 2/2] watchdog: cadence_wdt: Show information when driver is probed Michal Simek
2017-08-04 13:47 ` Guenter Roeck
2017-08-04 13:56 ` Michal Simek [this message]
2017-08-14 14:47 ` Guenter Roeck
2017-08-04 13:45 ` [PATCH 1/2] watchdog: cadence_wdt: Enable access to module parameters Guenter Roeck
2017-08-04 13:52 ` Michal Simek
2017-08-14 14:47 ` Guenter Roeck
2017-08-14 14:51 ` Michal Simek
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=e83dcbe3-a65f-d4d0-2922-5929eca45ea9@monstr.eu \
--to=monstr@monstr.eu \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-watchdog@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=michal.simek@xilinx.com \
--cc=wim@iguana.be \
/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®