From: Andrew Morton <akpm@linux-foundation.org>
To: Wolfram Sang <w.sang@pengutronix.de>
Cc: linux-watchdog@vger.kernel.org, rtc-linux@googlegroups.com,
Wim Van Sebroeck <wim@iguana.be>
Subject: Re: [PATCH RESEND 0/3] watchdog: new driver for STMP3xxx/MX23/MX28
Date: Tue, 24 Jan 2012 17:02:26 -0800 [thread overview]
Message-ID: <20120124170226.fa6386a1.akpm@linux-foundation.org> (raw)
In-Reply-To: <1327347185-620-1-git-send-email-w.sang@pengutronix.de>
On Mon, 23 Jan 2012 20:33:02 +0100
Wolfram Sang <w.sang@pengutronix.de> wrote:
> The first patch adds an accessor routine to the RTC-driver which can hopefully
> go via the watchdog-tree as well (asking for Andrew's ack here). The second
> patch adds the new driver, the third removes the old one.
I had a few little issues.
> After missing the last merge window, I really hope we can get it into 3.4. The
> old driver was broken (= not compilable) anyhow, so there cannot be any
> regression. Tested on a MX28EVK.
Well, people out could still be using the old driver after applying
local fixups.
How compatible is the new driver with the old one? Same module
parameters? Will it just transparently work? IOW, if people out there
are using the old driver now, how much will this sudden removal impact
them?
prev parent reply other threads:[~2012-01-25 1:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-23 19:33 [PATCH RESEND 0/3] watchdog: new driver for STMP3xxx/MX23/MX28 Wolfram Sang
2012-01-23 19:33 ` [PATCH 1/3] rtc: stmp3xxx: add wdt-accessor function Wolfram Sang
2012-01-25 0:59 ` Andrew Morton
2012-01-23 19:33 ` [PATCH 2/3] watchdog: add new driver for STMP3xxx and i.MX23/28 Wolfram Sang
2012-01-25 1:02 ` Andrew Morton [this message]
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=20120124170226.fa6386a1.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=linux-watchdog@vger.kernel.org \
--cc=rtc-linux@googlegroups.com \
--cc=w.sang@pengutronix.de \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.