From: linux@roeck-us.net (Guenter Roeck)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v4 1/9] watchdog: orion: Move the register ioremap'ing to its own function
Date: Sat, 15 Mar 2014 14:25:09 -0700 [thread overview]
Message-ID: <5324C535.6010009@roeck-us.net> (raw)
In-Reply-To: <1394907484-26002-2-git-send-email-ezequiel.garcia@free-electrons.com>
On 03/15/2014 11:17 AM, Ezequiel Garcia wrote:
> Follow-up patches will extend the registers ioremap and request
> to handle SoC-specific quirks on the RSTOUT register. Therefore,
> in order to keep the code readable, this commit introduces a special
> function for this.
>
> Signed-off-by: Ezequiel Garcia <ezequiel.garcia@free-electrons.com>
Reviewed-by: Guenter Roeck <linux@roeck-us.net>
next prev parent reply other threads:[~2014-03-15 21:25 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-15 18:17 [PATCH v4 0/9] Watchdog support for Armada 375/38x SoC Ezequiel Garcia
2014-03-15 18:17 ` [PATCH v4 1/9] watchdog: orion: Move the register ioremap'ing to its own function Ezequiel Garcia
2014-03-15 21:25 ` Guenter Roeck [this message]
2014-03-15 18:17 ` [PATCH v4 2/9] watchdog: orion: Introduce a SoC-specific RSTOUT mapping Ezequiel Garcia
2014-03-15 18:17 ` [PATCH v4 3/9] watchdog: orion: Remove unneeded atomic access Ezequiel Garcia
2014-03-15 18:17 ` [PATCH v4 4/9] watchdog: orion: Introduce per-SoC stop() function Ezequiel Garcia
2014-03-15 18:18 ` [PATCH v4 5/9] watchdog: orion: Introduce per-SoC enabled() function Ezequiel Garcia
2014-03-15 18:18 ` [PATCH v4 6/9] watchdog: orion: Add Armada 375/380 SoC support Ezequiel Garcia
2014-03-15 18:18 ` [PATCH v4 7/9] ARM: mvebu: Enable Armada 375 watchdog in the devicetree Ezequiel Garcia
2014-03-15 18:18 ` [PATCH v4 8/9] ARM: mvebu: Enable Armada 380/385 " Ezequiel Garcia
2014-03-15 18:18 ` [PATCH v4 9/9] ARM: mvebu: Add A375/A380 watchdog binding documentation Ezequiel Garcia
2014-03-17 19:10 ` [PATCH v4 0/9] Watchdog support for Armada 375/38x SoC Sebastian Hesselbarth
2014-03-17 20:47 ` Ezequiel Garcia
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=5324C535.6010009@roeck-us.net \
--to=linux@roeck-us.net \
--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).