From: Ralf Baechle <ralf@linux-mips.org>
To: Gabor Juhos <juhosg@openwrt.org>
Cc: linux-mips@linux-mips.org, Imre Kaloz <kaloz@openwrt.org>,
"Luis R. Rodriguez" <lrodriguez@atheros.com>,
Cliff Holden <Cliff.Holden@atheros.com>,
Kathy Giori <Kathy.Giori@atheros.com>,
Wim Van Sebroeck <wim@iguana.be>,
linux-watchdog@vger.kernel.org
Subject: Re: [PATCH v5 06/16] watchdog: add driver for the Atheros AR71XX/AR724X/AR913X SoCs
Date: Tue, 18 Jan 2011 00:29:06 +0100 [thread overview]
Message-ID: <20110117232906.GF12626@linux-mips.org> (raw)
In-Reply-To: <1294172909-1309-7-git-send-email-juhosg@openwrt.org>
Dropped as this one has already been merged via the watchdog tree.
Thanks folks,
Ralf
prev parent reply other threads:[~2011-01-17 23:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1294172909-1309-1-git-send-email-juhosg@openwrt.org>
2011-01-04 20:28 ` [PATCH v5 06/16] watchdog: add driver for the Atheros AR71XX/AR724X/AR913X SoCs Gabor Juhos
2011-01-17 23:29 ` Ralf Baechle [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=20110117232906.GF12626@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=Cliff.Holden@atheros.com \
--cc=Kathy.Giori@atheros.com \
--cc=juhosg@openwrt.org \
--cc=kaloz@openwrt.org \
--cc=linux-mips@linux-mips.org \
--cc=linux-watchdog@vger.kernel.org \
--cc=lrodriguez@atheros.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;
as well as URLs for NNTP newsgroup(s).