From: will.deacon@arm.com (Will Deacon)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] iommu: Make of_device_id array const
Date: Thu, 11 Sep 2014 14:51:19 +0100 [thread overview]
Message-ID: <20140911135119.GH6158@arm.com> (raw)
In-Reply-To: <1410442656-21112-1-git-send-email-kiran.padwal@smartplayin.com>
On Thu, Sep 11, 2014 at 02:37:36PM +0100, Kiran Padwal wrote:
> Make of_device_id array const, because all OF functions handle it as const.
>
> Signed-off-by: Kiran Padwal <kiran.padwal@smartplayin.com>
> ---
> drivers/iommu/arm-smmu.c | 2 +-
> drivers/iommu/omap-iommu.c | 2 +-
> drivers/iommu/tegra-gart.c | 2 +-
> drivers/iommu/tegra-smmu.c | 2 +-
> 4 files changed, 4 insertions(+), 4 deletions(-)
Ha, I've seen a few of these patches recently. Did some tool just get
support for detecting this?
Anyway, looks fine and should probably go via Joerg.
Will
next prev parent reply other threads:[~2014-09-11 13:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-11 13:37 [PATCH] iommu: Make of_device_id array const Kiran Padwal
2014-09-11 13:51 ` Will Deacon [this message]
2014-09-12 12:44 ` kiran.padwal at smartplayin.com
2014-09-25 14:01 ` Joerg Roedel
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=20140911135119.GH6158@arm.com \
--to=will.deacon@arm.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).