From: Daniel Lezcano <daniel.lezcano@linaro.org>
To: ysato@users.sourceforge.jp
Cc: tglx@linutronix.de, linux-kernel@vger.kernel.org,
Jason Cooper <jason@lakedaemon.net>,
Marc Zyngier <marc.zyngier@arm.com>,
"moderated list:H8/300 ARCHITECTURE"
<uclinux-h8-devel@lists.sourceforge.jp>
Subject: Re: [PATCH 1/3] h8300: Rename ctlr_out/in[bwl] to raw_read/write[bwl]
Date: Mon, 9 Nov 2015 15:38:19 +0100 [thread overview]
Message-ID: <5640AFDB.7010904@linaro.org> (raw)
In-Reply-To: <1447079782-26027-1-git-send-email-daniel.lezcano@linaro.org>
On 11/09/2015 03:36 PM, Daniel Lezcano wrote:
> For the sake of consistency, let rename all ctrl_out/in calls to the write/read
> calls so we have the same API consistent with the other architectures hence
> open the door for the increasing of the test compilation coverage.
>
> The unsigned long coercive cast is removed because all variables are set to
> the right type "void __iomem *".
>
> Signed-off-by: Daniel Lezcano <daniel.lezcano@linaro.org>
Series compiled on X86, ARM, ARM64, PARISC and H8300. Not tested.
--
<http://www.linaro.org/> Linaro.org │ Open source software for ARM SoCs
Follow Linaro: <http://www.facebook.com/pages/Linaro> Facebook |
<http://twitter.com/#!/linaroorg> Twitter |
<http://www.linaro.org/linaro-blog/> Blog
next prev parent reply other threads:[~2015-11-09 14:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-09 14:36 Daniel Lezcano
2015-11-09 14:36 ` [PATCH 2/3] clocksource/drivers/h8300_timer8: Separate the Kconfig option from the arch Daniel Lezcano
2015-11-09 14:36 ` [PATCH 3/3] clocksource/drivers/h8300: Increase the compilation test coverage Daniel Lezcano
2015-11-09 14:38 ` Daniel Lezcano [this message]
2015-11-11 5:52 ` [PATCH 1/3] h8300: Rename ctlr_out/in[bwl] to raw_read/write[bwl] Daniel Lezcano
2015-11-11 15:01 ` Yoshinori Sato
2015-11-14 11:49 ` [PATCH] h8300: Replace read/write to ioread/write Yoshinori Sato
2015-11-18 22:28 ` Stephen Boyd
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=5640AFDB.7010904@linaro.org \
--to=daniel.lezcano@linaro.org \
--cc=jason@lakedaemon.net \
--cc=linux-kernel@vger.kernel.org \
--cc=marc.zyngier@arm.com \
--cc=tglx@linutronix.de \
--cc=uclinux-h8-devel@lists.sourceforge.jp \
--cc=ysato@users.sourceforge.jp \
/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
Powered by JetHome