From: u.kleine-koenig@pengutronix.de (Uwe Kleine-König)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/3] ARM: mx5: add support for the two watchdog modules
Date: Tue, 7 Dec 2010 14:08:07 +0100 [thread overview]
Message-ID: <20101207130807.GF21020@pengutronix.de> (raw)
In-Reply-To: <AANLkTi=1ugnEX=f4Ko=d=7JWr5LZtTK+9L6ZWGt0Epth@mail.gmail.com>
Hi Fabio,
On Tue, Dec 07, 2010 at 09:06:09AM -0200, Fabio Estevam wrote:
> 2010/12/7 Uwe Kleine-K?nig <u.kleine-koenig@pengutronix.de>:
> > On Mon, Dec 06, 2010 at 04:38:32PM -0200, Fabio Estevam wrote:
> >> MX51 has two watchdog modules.
> >>
> >> Add support for both of them.
> > I don't know why you need two watchdogs, but the patches look OK.
>
> Can I get your Acked-by?
Yeah, you can consider that as an ack for the three patches in this
series.
> > Note there is a conflict between this patch series and the clk-change
> > for the watchdog driver.
>
> Yes, I am aware of it. Probably the watchod driver patch I sent will
> go via the watchdog maintainer and when it gets applied I can fix the
> clocks for mx5 watchdog.
Hmm, maybe it's easier to let it go via Sascha's tree because it is more
likely to conflict with the changes there.
Uwe
--
Pengutronix e.K. | Uwe Kleine-K?nig |
Industrial Linux Solutions | http://www.pengutronix.de/ |
prev parent reply other threads:[~2010-12-07 13:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-06 18:38 [PATCH 1/3] ARM: mx5: add support for the two watchdog modules Fabio Estevam
2010-12-06 18:38 ` [PATCH 2/3] ARM: mx5: add watchdog clocks Fabio Estevam
2010-12-06 18:38 ` [PATCH 3/3] ARM: mx5/mx51_babbage: Add watchdog support Fabio Estevam
2010-12-07 9:16 ` [PATCH 1/3] ARM: mx5: add support for the two watchdog modules Uwe Kleine-König
2010-12-07 11:06 ` Fabio Estevam
2010-12-07 13:08 ` Uwe Kleine-König [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=20101207130807.GF21020@pengutronix.de \
--to=u.kleine-koenig@pengutronix.de \
--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).