From: Guenter Roeck <linux@roeck-us.net>
To: Pratyush Anand <panand@redhat.com>, linux-watchdog@vger.kernel.org
Cc: dyoung@redhat.com, dzickus@redhat.com
Subject: Re: [PATCH 00/37] watchdog: Fix parent of watchdog devices
Date: Tue, 18 Aug 2015 08:48:39 -0700 [thread overview]
Message-ID: <55D353D7.4020904@roeck-us.net> (raw)
In-Reply-To: <cover.1439524806.git.panand@redhat.com>
On 08/17/2015 09:47 PM, Pratyush Anand wrote:
> Hi,
>
> I posted a query here (https://lkml.org/lkml/2015/8/10/19), but did not get any
> feedback. So, thought to post patches and to seek response.
>
> I need some way to identify the driver/module for a given watchdog node say
> /dev/watchdog0.
>
> Documentation/watchdog/watchdog-api.txt says:
> identity a string identifying the watchdog driver
>
> However, all the watchdog driver does not define identity as DRV_NAME.
>
> Otherway could be to look for /sys/class/watchdog/watchdog0/device/modalias.
>
> However, many wdt devices does not set its parent and so, we do not see an entry
> for /sys/class/watchdog/watchdog0/device/ in sysfs.
>
> This patch set fixes parent for wdt drivers written in watchdog-core framework.
>
> Exceptions: booke, diag288, mpc8xxx, octeon, softdog and w83627hf -- They do not
> have any parent. Not sure, how we can identify driver for these devices.
>
Series makes sense, but imposes a huge burden on the maintainer.
I think this is one of those changes where a single patch would make much more sense.
I merged all patches into my test repository for build and runtime tests,
but I would suggest to resubmit the series as a single patch.
Thanks,
Guenter
next prev parent reply other threads:[~2015-08-18 15:48 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-18 4:47 [PATCH 00/37] watchdog: Fix parent of watchdog devices Pratyush Anand
2015-08-18 4:47 ` [PATCH 01/37] mei: wd: Fix parent of watchdog_device Pratyush Anand
2015-08-18 4:47 ` [PATCH 02/37] watchdog: wm8350: " Pratyush Anand
2015-08-18 4:47 ` [PATCH 03/37] watchdog: wm831x: " Pratyush Anand
2015-08-18 4:47 ` [PATCH 04/37] watchdog: via: " Pratyush Anand
2015-08-18 4:47 ` [PATCH 05/37] watchdog: ux500: " Pratyush Anand
2015-08-18 4:47 ` [PATCH 06/37] watchdog: txx9wdt: " Pratyush Anand
2015-08-18 4:47 ` [PATCH 07/37] watchdog: twl4030: " Pratyush Anand
2015-08-18 4:47 ` [PATCH 08/37] watchdog: tegra: " Pratyush Anand
2015-08-18 4:47 ` [PATCH 09/37] watchdog: stmp3xxx_rtc: " Pratyush Anand
2015-08-18 4:47 ` [PATCH 10/37] watchdog: st_lpc: " Pratyush Anand
2015-08-18 6:38 ` Lee Jones
2015-08-18 4:47 ` [PATCH 11/37] watchdog: sp805: " Pratyush Anand
2015-08-18 6:41 ` Viresh Kumar
2015-08-18 4:47 ` [PATCH 12/37] watchdog: sirfsoc: " Pratyush Anand
2015-08-18 4:47 ` [PATCH 13/37] watchdog: sh: " Pratyush Anand
2015-08-18 4:47 ` [PATCH 14/37] watchdog: s3c2410: " Pratyush Anand
2015-08-18 4:47 ` [PATCH 15/37] watchdog: rt2880: " Pratyush Anand
2015-08-18 4:47 ` [PATCH 16/37] watchdog: retu: " Pratyush Anand
2015-08-18 4:47 ` [PATCH 17/37] watchdog: qcom: " Pratyush Anand
2015-08-18 4:47 ` [PATCH 18/37] watchdog: pnx4008: " Pratyush Anand
2015-08-18 4:47 ` [PATCH 19/37] watchdog: orion: " Pratyush Anand
2015-08-18 4:47 ` [PATCH 20/37] watchdog: omap: " Pratyush Anand
2015-08-18 4:47 ` [PATCH 21/37] watchdog: menf21bmc: " Pratyush Anand
2015-08-18 4:47 ` [PATCH 22/37] watchdog: mena21: " Pratyush Anand
2015-08-18 6:48 ` Johannes Thumshirn
2015-08-18 4:47 ` [PATCH 23/37] watchdog: jz4740: " Pratyush Anand
2015-08-18 4:47 ` [PATCH 24/37] watchdog: intel-mid: " Pratyush Anand
2015-08-20 18:24 ` David Cohen
2015-08-18 4:47 ` [PATCH 25/37] watchdog: ie6xx: " Pratyush Anand
2015-08-18 4:47 ` [PATCH 26/37] watchdog: gpio: " Pratyush Anand
2015-08-18 4:48 ` [PATCH 27/37] watchdog: ep93xx: " Pratyush Anand
2015-08-18 4:48 ` [PATCH 28/37] watchdog: digicolor: " Pratyush Anand
2015-08-18 5:41 ` Baruch Siach
2015-08-18 6:03 ` Pratyush Anand
2015-08-18 4:48 ` [PATCH 29/37] watchdog: davinci: " Pratyush Anand
2015-08-18 4:48 ` [PATCH 30/37] watchdog: da9063: " Pratyush Anand
2015-08-18 4:48 ` [PATCH 31/37] watchdog: da9062: " Pratyush Anand
2015-08-18 4:48 ` [PATCH 32/37] watchdog: da9055: " Pratyush Anand
2015-08-18 4:48 ` [PATCH 33/37] watchdog: da9052: " Pratyush Anand
2015-08-18 4:48 ` [PATCH 34/37] watchdog: coh901327: " Pratyush Anand
2015-08-18 4:48 ` [PATCH 35/37] watchdog: bcm_kona: " Pratyush Anand
2015-08-18 4:48 ` [PATCH 36/37] watchdog: bcm47xx: " Pratyush Anand
2015-08-18 4:48 ` [PATCH 37/37] watchdog: bcm2835: " Pratyush Anand
2015-08-18 20:25 ` Lubomir Rintel
2015-08-18 15:48 ` Guenter Roeck [this message]
2015-08-18 16:39 ` [PATCH 00/37] watchdog: Fix parent of watchdog devices Pratyush Anand
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=55D353D7.4020904@roeck-us.net \
--to=linux@roeck-us.net \
--cc=dyoung@redhat.com \
--cc=dzickus@redhat.com \
--cc=linux-watchdog@vger.kernel.org \
--cc=panand@redhat.com \
/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