From: Hans de Goede <hdegoede@redhat.com>
To: Wim Van Sebroeck <wim@iguana.be>
Cc: "Alan Cox" <alan@lxorguk.ukuu.org.uk>,
linux-watchdog@vger.kernel.org,
"LM Sensors" <lm-sensors@lm-sensors.org>,
"Thilo Cestonaro" <thilo.cestonaro@ts.fujitsu.com>,
"Pádraig Brady" <P@draigBrady.com>
Subject: Re: [PATCH 1/3] watchdog_dev: Add support for having more then 1 watchdog
Date: Mon, 07 May 2012 08:58:00 +0200 [thread overview]
Message-ID: <4FA77278.5030705@redhat.com> (raw)
In-Reply-To: <20120504123434.GR3074@spo001.leaseweb.com>
Hi,
On 05/04/2012 02:34 PM, Wim Van Sebroeck wrote:
> Hi Alan,
>
>>> You do this even for watchdog0 / for the watchdog we've also registered as
>>> misc_dev. I guess this is intentional and you want the watchdog to be
>>> available as both misc,130 as well as as MAJOR(dog_devt),0 ?
>>
>> Yes - so that it appears in the watchdog class in sysfs for example.
>
> What happens if one program opens the miscdevice and another program opens the MAJOR(dog_devt),0 device?
> I presume that the WDOG_DEV_OPEN status bit will prohibit the opening of the second device in that case...
Correct.
Regards,
Hans
next prev parent reply other threads:[~2012-05-07 6:58 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-15 11:59 Watchdog timer core enhancements Hans de Goede
2012-03-15 11:59 ` [PATCH 1/3] watchdog_dev: Add support for having more then 1 watchdog Hans de Goede
2012-03-15 13:11 ` Alan Cox
2012-03-15 14:18 ` Hans de Goede
2012-03-15 15:38 ` Alan Cox
2012-05-04 12:34 ` Wim Van Sebroeck
2012-05-07 6:58 ` Hans de Goede [this message]
2012-03-15 11:59 ` [PATCH 2/3] watchdog_dev: Add support for dynamically allocated watchdog_device structs Hans de Goede
2012-03-15 11:59 ` [PATCH 3/3] watchdog_dev: Let the driver update the timeout field on set_timeout success Hans de Goede
2012-03-15 12:39 ` Watchdog timer core enhancements Pádraig Brady
2012-03-15 21:13 ` Wim Van Sebroeck
2012-03-16 7:43 ` Hans de Goede
2012-03-17 12:56 ` Wolfram Sang
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=4FA77278.5030705@redhat.com \
--to=hdegoede@redhat.com \
--cc=P@draigBrady.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-watchdog@vger.kernel.org \
--cc=lm-sensors@lm-sensors.org \
--cc=thilo.cestonaro@ts.fujitsu.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;
as well as URLs for NNTP newsgroup(s).