Linux Watchdog driver development
 help / color / mirror / Atom feed
From: Hans de Goede <hdegoede@redhat.com>
To: Wim Van Sebroeck <wim@iguana.be>
Cc: Tomas Winkler <tomas.winkler@intel.com>,
	"linux-watchdog@vger.kernel.org" <linux-watchdog@vger.kernel.org>,
	Alan Cox <alan@linux.intel.com>
Subject: Re: [PATCH 1/2 V3] watchdog: Add multiple device support
Date: Tue, 22 May 2012 18:51:52 +0200	[thread overview]
Message-ID: <4FBBC428.4010400@redhat.com> (raw)
In-Reply-To: <20120522164124.GF3074@spo001.leaseweb.com>

Hi,

On 05/22/2012 06:41 PM, Wim Van Sebroeck wrote:
> Hi Hans,
>
>>>> Thanks for clarification.
>>>> BTW the patch is gone again from the tree.
>>>
>>> Patches are back but I added some small fixes:
>>> * watchdog_dev.h should have been watchdog_core.h
>>> * the file should have been using extern for the function prototypes.
>>> * introduce subsys_initcall instead of module_init and move that also to
>>> the core.
>>> * make subsys_initcall and module_exit static
>>> * moved device create code into watchdog_core where it belongs
>>> * changed busdev to parent
>>> * integrated Hans's documentation into the respective patches.
>>>
>>> Please have a look and test.
>>
>> Thanks for all the work on merging this, I've re-reviewed the set and
>> tested it with my convert sch56xx watchdog to the wdog-core patchset.
>>
>> Everything looks good and works as advertised :)
>>
>> I've rebased my sch56xx watchdog patchset as my patch titled:
>> "watchdog_dev: Add support for dynamically allocated watchdog_device
>> structs"
>> needed rebasing, I'll re-send it after this mail.
>
> I will split your "watchdog_dev: Add support for dynamically allocated
> watchdog_device structs" patch into 3 patches:
> 1) rewriting of wrappers (and I will add some extra code to it for
> the get_timeleft ioctl).
> 2) locking
> 3) ref+unref+unregistered.

Sounds good! Assuming you manage to finish this tonight, I'll review
and test first thing tomorrow morning.

Regards,

Hans

  reply	other threads:[~2012-05-22 16:47 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-14 13:29 [PATCH 1/2 V3] watchdog: Add multiple device support Tomas Winkler
2012-05-14 13:29 ` [PATCH 2/2 V3] watchdog: create all the proper device files Tomas Winkler
2012-05-14 13:52 ` [PATCH 1/2 V3] watchdog: Add multiple device support Wim Van Sebroeck
2012-05-14 14:00   ` Winkler, Tomas
2012-05-14 17:30     ` Tomas Winkler
2012-05-17  7:19       ` Wim Van Sebroeck
2012-05-17 11:30         ` Tomas Winkler
2012-05-21 20:21           ` Wim Van Sebroeck
2012-05-22  9:36             ` Hans de Goede
2012-05-22 16:41               ` Wim Van Sebroeck
2012-05-22 16:51                 ` Hans de Goede [this message]
2012-05-22 21:18                   ` Wim Van Sebroeck
2012-05-23  8:47                     ` Hans de Goede
2012-05-22 10:53             ` Tomas Winkler
2012-05-22 16:38               ` Wim Van Sebroeck
2012-05-14 14:01 ` Wim Van Sebroeck
2012-05-14 14:07   ` Winkler, Tomas

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=4FBBC428.4010400@redhat.com \
    --to=hdegoede@redhat.com \
    --cc=alan@linux.intel.com \
    --cc=linux-watchdog@vger.kernel.org \
    --cc=tomas.winkler@intel.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