From: tip-bot for Bhumika Goyal <tipbot@zytor.com>
To: linux-tip-commits@vger.kernel.org
Cc: mingo@kernel.org, tglx@linutronix.de, hpa@zytor.com,
bhumirks@gmail.com, linux-kernel@vger.kernel.org
Subject: [tip:x86/cleanups] x86/events/amd/iommu: Make iommu_pmu const and __initconst
Date: Thu, 19 Oct 2017 07:19:16 -0700 [thread overview]
Message-ID: <tip-642e641cbea57e559720b9df09889ffcf525cf04@git.kernel.org> (raw)
In-Reply-To: <1505819443-670-1-git-send-email-bhumirks@gmail.com>
Commit-ID: 642e641cbea57e559720b9df09889ffcf525cf04
Gitweb: https://git.kernel.org/tip/642e641cbea57e559720b9df09889ffcf525cf04
Author: Bhumika Goyal <bhumirks@gmail.com>
AuthorDate: Tue, 19 Sep 2017 16:40:43 +0530
Committer: Thomas Gleixner <tglx@linutronix.de>
CommitDate: Thu, 19 Oct 2017 16:15:47 +0200
x86/events/amd/iommu: Make iommu_pmu const and __initconst
iommu_pmu is only used as source for a copy operation in the init code
path.
Mark it const and __initconst.
Signed-off-by: Bhumika Goyal <bhumirks@gmail.com>
Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
Cc: julia.lawall@lip6.fr
Link: https://lkml.kernel.org/r/1505819443-670-1-git-send-email-bhumirks@gmail.com
---
arch/x86/events/amd/iommu.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/x86/events/amd/iommu.c b/arch/x86/events/amd/iommu.c
index 3641e24..38b5d41 100644
--- a/arch/x86/events/amd/iommu.c
+++ b/arch/x86/events/amd/iommu.c
@@ -405,7 +405,7 @@ const struct attribute_group *amd_iommu_attr_groups[] = {
NULL,
};
-static struct pmu iommu_pmu = {
+static const struct pmu iommu_pmu __initconst = {
.event_init = perf_iommu_event_init,
.add = perf_iommu_add,
.del = perf_iommu_del,
prev parent reply other threads:[~2017-10-19 14:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-19 11:10 [PATCH] x86/events/amd/iommu: make iommu_pmu const and __initconst Bhumika Goyal
2017-10-19 14:19 ` tip-bot for Bhumika Goyal [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=tip-642e641cbea57e559720b9df09889ffcf525cf04@git.kernel.org \
--to=tipbot@zytor.com \
--cc=bhumirks@gmail.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=tglx@linutronix.de \
/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).