From: peter.fordham@gmail.com (Peter Fordham)
To: linux-arm-kernel@lists.infradead.org
Subject: [MPCore Watchdog]: Convert from misc_dev to dynamic device node.
Date: Wed, 15 Jun 2011 12:49:43 -0700 [thread overview]
Message-ID: <BANLkTi=_DDxRqhqi=9Me6gWmm2h3wb5Zng@mail.gmail.com> (raw)
In-Reply-To: <201106152136.23971.arnd@arndb.de>
On 15 June 2011 12:36, Arnd Bergmann <arnd@arndb.de> wrote:
> Let's first wait until the generic watchdog framework gets merged and
> the drivers are converted. After that is in, we can discuss further changes.
That seems logical and reasonable. Are we saying no changes to watchdog
drivers in general until this is done? because I have other patches
for this driver
that among other things actually make it work properly. As it stands today
the timeout calculations are broken which results in random reboots.
The framework patch was submitted 3.5 months ago and isn't in yet. Is it held up
on something? I don't see any negative comments.
> I highly doubt that making an incompatible API change benefits anyone here,
> but it certainly shouldn't be done for a single driver that is separate from
> the framework.
Not to be a pedant but, this doesn't change the API at all.
-Pete
next prev parent reply other threads:[~2011-06-15 19:49 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-14 23:29 [MPCore Watchdog]: Convert from misc_dev to dynamic device node Peter Fordham
2011-06-14 23:48 ` Jamie Iles
2011-06-15 0:19 ` Peter Fordham
2011-06-15 8:58 ` Jamie Iles
2011-06-15 18:57 ` Peter Fordham
2011-06-15 19:09 ` Jamie Iles
2011-06-15 19:36 ` Peter Fordham
2011-06-15 19:37 ` Peter Fordham
2011-06-15 19:36 ` Arnd Bergmann
2011-06-15 19:49 ` Peter Fordham [this message]
2011-06-15 20:03 ` Arnd Bergmann
2011-06-17 7:20 ` Wim Van Sebroeck
2011-06-17 7:17 ` Wim Van Sebroeck
2011-06-17 7:14 ` Wim Van Sebroeck
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='BANLkTi=_DDxRqhqi=9Me6gWmm2h3wb5Zng@mail.gmail.com' \
--to=peter.fordham@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
/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).