[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <ADE657CA350FB648AAC2C43247A983F001F383E05C4A@AUSP01VMBX24.collaborationhost.net>
Date: Thu, 14 Jul 2011 15:10:37 -0500
From: H Hartley Sweeten <hartleys@...ionengravers.com>
To: Wolfram Sang <w.sang@...gutronix.de>
CC: "linux-watchdog@...r.kernel.org" <linux-watchdog@...r.kernel.org>,
"wim@...ana.be" <wim@...ana.be>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"linux-arm-kernel@...ts.infradead.org"
<linux-arm-kernel@...ts.infradead.org>,
"tim.bird@...sony.com" <tim.bird@...sony.com>
Subject: RE: [RFC 0/6] watchdog drivers converted to the new framework
On Thursday, July 14, 2011 1:01 PM, Wolfram Sang wrote:
> On Thu, Jul 14, 2011 at 01:42:02PM -0500, H Hartley Sweeten wrote:
>> On Thursday, July 14, 2011 11:28 AM, Wolfram Sang wrote:
>>>> I would also like to convert this driver into a proper platform_driver using
>>>> ioremap'ed addresses instead of the static mappings. Converting the driver
>>>> to the new watchdog framework would make this a bit cleaner.
>>>
>>> Try managed devices (devm_* and friends) for an extra cleanup bonus.
>>
>> Already done, just waiting for the framework... ;-)
>
> Nice :) Did you use my conversion-guide as a reference? Any comments if so?
Sorry, I didn't. I just worked it out from the framework core and looking
at your examples.
When I found the framework patches on lkml I couldn't get them into a state
to apply to my tree. I ended up manually applying all the pieces so I skipped
the Documentation stuff to save some time.
The conversion is pretty straight forward after examining the watchdog
framework files.
Regards,
Hartley--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists