From: Guenter Roeck <linux@roeck-us.net>
To: Radu Rendec <rrendec@arista.com>
Cc: Wim Van Sebroeck <wim@iguana.be>, linux-watchdog@vger.kernel.org
Subject: Re: [PATCH v3 0/2] xen_wdt: use the watchdog subsystem
Date: Tue, 14 Nov 2017 09:31:11 -0800 [thread overview]
Message-ID: <20171114173111.GA2237@roeck-us.net> (raw)
In-Reply-To: <20171114162350.24283-1-rrendec@arista.com>
On Tue, Nov 14, 2017 at 04:23:48PM +0000, Radu Rendec wrote:
> Hi Guenter,
>
> Attaching v3 of the xen_wdt patch, including the dev_info() fix. Please
> note that I had to make some additional changes to make this work - as
> described in my previous email (included below for your convenience).
>
> 8<----------------------------------------------------------------------
>
> On Sat, 2017-11-11 at 08:40 -0800, Guenter Roeck wrote:
> > dev_info has that odd "wdt: " header because DRV_NAME is set to "wdt",
> > which doesn't really make much sense. Please use something more sensible
> > for DRV_NAME and use dev_info.
>
> The trouble is (was) that the device is matched against the driver by
> the name, so the device name has to be the same as the driver name.
> Then, regardless of what the name is, __dev_printk() will print it
> twice (once as the driver name and once as the device name).
>
Isn't that rather because MODULE_ALIAS is missing in the driver ?
Guenter
> As a workaround, after looking at platform_match(), I added an id_table
> to the platform_driver struct and now the match is done by that. Then
> the driver name can be different.
>
> I set the driver name to "xen_wdt" and the device name to "watchdog".
> Now the messages (using dev_info()) look like this:
>
> xen_wdt watchdog: initialized (timeout=60s, nowayout=0)
>
> At least this looks more meaningful; I hope it's ok.
>
> 8<----------------------------------------------------------------------
>
> Radu Rendec (2):
> watchdog: xen_wdt: use the watchdog subsystem
> watchdog: xen_wdt: remove info message and version number
>
> drivers/watchdog/xen_wdt.c | 258 +++++++++++----------------------------------
> 1 file changed, 59 insertions(+), 199 deletions(-)
>
> --
> 2.13.6
>
next prev parent reply other threads:[~2017-11-14 17:31 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-14 16:23 [PATCH v3 0/2] xen_wdt: use the watchdog subsystem Radu Rendec
2017-11-14 16:23 ` [PATCH v3 1/2] watchdog: " Radu Rendec
2017-11-15 14:58 ` Guenter Roeck
2017-11-15 15:34 ` Radu Rendec
2017-11-15 16:26 ` Guenter Roeck
2017-11-15 16:46 ` Radu Rendec
2017-11-15 18:21 ` Guenter Roeck
2017-11-14 16:23 ` [PATCH v3 2/2] watchdog: xen_wdt: remove info message and version number Radu Rendec
2017-11-14 17:31 ` Guenter Roeck [this message]
2017-11-14 18:08 ` [PATCH v3 0/2] xen_wdt: use the watchdog subsystem Radu Rendec
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=20171114173111.GA2237@roeck-us.net \
--to=linux@roeck-us.net \
--cc=linux-watchdog@vger.kernel.org \
--cc=rrendec@arista.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