From: joro@8bytes.org (Joerg Roedel)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] iommu/exynos: Use proper readl/writel register interface
Date: Mon, 29 Feb 2016 16:46:06 +0100 [thread overview]
Message-ID: <20160229154606.GB13711@8bytes.org> (raw)
In-Reply-To: <1456749777-8998-1-git-send-email-m.szyprowski@samsung.com>
On Mon, Feb 29, 2016 at 01:42:57PM +0100, Marek Szyprowski wrote:
> Drivers should use generic readl/writel calls to access HW registers, so
> replace all __raw_readl/writel with generic version.
>
> Suggested-by: Arnd Bergmann <arnd@arndb.de>
> Signed-off-by: Marek Szyprowski <m.szyprowski@samsung.com>
> ---
> drivers/iommu/exynos-iommu.c | 38 +++++++++++++++++++-------------------
> 1 file changed, 19 insertions(+), 19 deletions(-)
Applied, thanks.
prev parent reply other threads:[~2016-02-29 15:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-29 12:42 [PATCH] iommu/exynos: Use proper readl/writel register interface Marek Szyprowski
2016-02-29 12:45 ` Arnd Bergmann
2016-02-29 15:46 ` Joerg Roedel [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=20160229154606.GB13711@8bytes.org \
--to=joro@8bytes.org \
--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).