From: Arvind Yadav <arvind.yadav.cs@gmail.com>
To: m.szyprowski@samsung.com, joro@8bytes.org, kgene@kernel.org,
krzk@kernel.org, matthias.bgg@gmail.com,
gerald.schaefer@de.ibm.com
Cc: linux-kernel@vger.kernel.org, iommu@lists.linux-foundation.org,
linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/3] constify iommu_ops
Date: Mon, 28 Aug 2017 17:41:37 +0530 [thread overview]
Message-ID: <1503922298-25862-1-git-send-email-arvind.yadav.cs@gmail.com> (raw)
iommu_ops are not supposed to change at runtime.
Functions 'iommu_device_set_ops' and 'bus_set_iommu' working with
const iommu_ops provided by <linux/iommu.h>. So mark the non-const
structs as const.
Arvind Yadav (3):
[PATCH 1/3] iommu: exynos: constify iommu_ops
[PATCH 2/3] iommu: mtk: constify iommu_ops
[PATCH 3/3] iommu: s390: constify iommu_ops
drivers/iommu/exynos-iommu.c | 4 ++--
drivers/iommu/mtk_iommu.c | 4 ++--
drivers/iommu/mtk_iommu_v1.c | 4 ++--
drivers/iommu/s390-iommu.c | 2 +-
4 files changed, 7 insertions(+), 7 deletions(-)
--
1.9.1
WARNING: multiple messages have this Message-ID (diff)
From: arvind.yadav.cs@gmail.com (Arvind Yadav)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/3] constify iommu_ops
Date: Mon, 28 Aug 2017 17:41:37 +0530 [thread overview]
Message-ID: <1503922298-25862-1-git-send-email-arvind.yadav.cs@gmail.com> (raw)
iommu_ops are not supposed to change at runtime.
Functions 'iommu_device_set_ops' and 'bus_set_iommu' working with
const iommu_ops provided by <linux/iommu.h>. So mark the non-const
structs as const.
Arvind Yadav (3):
[PATCH 1/3] iommu: exynos: constify iommu_ops
[PATCH 2/3] iommu: mtk: constify iommu_ops
[PATCH 3/3] iommu: s390: constify iommu_ops
drivers/iommu/exynos-iommu.c | 4 ++--
drivers/iommu/mtk_iommu.c | 4 ++--
drivers/iommu/mtk_iommu_v1.c | 4 ++--
drivers/iommu/s390-iommu.c | 2 +-
4 files changed, 7 insertions(+), 7 deletions(-)
--
1.9.1
next reply other threads:[~2017-08-28 12:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-28 12:11 Arvind Yadav [this message]
2017-08-28 12:11 ` [PATCH 0/3] constify iommu_ops Arvind Yadav
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=1503922298-25862-1-git-send-email-arvind.yadav.cs@gmail.com \
--to=arvind.yadav.cs@gmail.com \
--cc=gerald.schaefer@de.ibm.com \
--cc=iommu@lists.linux-foundation.org \
--cc=joro@8bytes.org \
--cc=kgene@kernel.org \
--cc=krzk@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=m.szyprowski@samsung.com \
--cc=matthias.bgg@gmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.