From: sameo@linux.intel.com (Samuel Ortiz)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/4] add ux500_wdt support
Date: Sun, 3 Feb 2013 18:07:18 +0100 [thread overview]
Message-ID: <20130203170718.GR8476@sortiz-mobl> (raw)
In-Reply-To: <1358509214-22407-1-git-send-email-fabio.baltieri@linaro.org>
Hi Fabio,
On Fri, Jan 18, 2013 at 12:40:10PM +0100, Fabio Baltieri wrote:
> Hi all,
>
> this set adds support for the ux500_wdt timer, implemented in the PRCMU
> unit of ST-Ericsson ux500 architecture.
>
> The first two patches add the necessary definitions and function export
> to the PRCMU driver currently in mainline, while the third an fourth
> patches add the actual watchdog driver and mfd_cell definition to make
> it probe when PRCMU is compiled in.
>
> As the patches touches files in both mfd and watchdog subsystems, what do
> you think is the best way to handle this set?
>
> Thanks,
> Fabio
>
>
> Fabio Baltieri (4):
> mfd: dbx500-prcmu: add watchdog ID definitions
> mfd: dbx500-prcmu: export a9wdog functions
> watchdog: add support for ux500_wdt watchdog
> mfd: db8500-prcmu: add ux500_wdt mfd_cell
All 4 patches (v2 for #3) applied, many thanks.
Cheers,
Samuel.
--
Intel Open Source Technology Centre
http://oss.intel.com/
prev parent reply other threads:[~2013-02-03 17:07 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-18 11:40 [PATCH 0/4] add ux500_wdt support Fabio Baltieri
2013-01-18 11:40 ` [PATCH 1/4] mfd: dbx500-prcmu: add watchdog ID definitions Fabio Baltieri
2013-01-18 11:40 ` [PATCH 2/4] mfd: dbx500-prcmu: export a9wdog functions Fabio Baltieri
2013-01-18 11:40 ` [PATCH 3/4] watchdog: add support for ux500_wdt watchdog Fabio Baltieri
2013-01-22 3:27 ` Samuel Ortiz
[not found] ` <20130128211222.GA3338@spo001.leaseweb.com>
2013-01-29 8:43 ` Fabio Baltieri
2013-01-29 8:57 ` [PATCH v2 " Fabio Baltieri
2013-01-18 11:40 ` [PATCH 4/4] mfd: db8500-prcmu: add ux500_wdt mfd_cell Fabio Baltieri
2013-01-21 14:50 ` [PATCH 0/4] add ux500_wdt support Linus Walleij
2013-02-03 17:07 ` Samuel Ortiz [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=20130203170718.GR8476@sortiz-mobl \
--to=sameo@linux.intel.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).