From: Bhumika Goyal <bhumirks@gmail.com>
To: julia.lawall@lip6.fr, linux-kernel@vger.kernel.org,
mark.rutland@arm.com, marc.zyngier@arm.com,
daniel.lezcano@linaro.org, tglx@linutronix.de,
linux-arm-kernel@lists.infradead.org, keescook@chromium.org
Cc: Bhumika Goyal <bhumirks@gmail.com>
Subject: [PATCH] clocksource: add __ro_after_init to cyclecounter
Date: Sun, 12 Feb 2017 00:50:18 +0530 [thread overview]
Message-ID: <1486840818-22214-1-git-send-email-bhumirks@gmail.com> (raw)
The object cyclecounter of type cyclecounter is not getting modified
after getting initialized by arch_counter_register. Apart from
initialization in arch_counter_register it is also passed as an argument
to the function timecounter_init but this argument is of type const.
Therefore, add __ro_after_init to its declaration.
Signed-off-by: Bhumika Goyal <bhumirks@gmail.com>
---
drivers/clocksource/arm_arch_timer.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/clocksource/arm_arch_timer.c b/drivers/clocksource/arm_arch_timer.c
index 4c8c3fb..a10506b 100644
--- a/drivers/clocksource/arm_arch_timer.c
+++ b/drivers/clocksource/arm_arch_timer.c
@@ -580,7 +580,7 @@ static u64 arch_counter_read_cc(const struct cyclecounter *cc)
.flags = CLOCK_SOURCE_IS_CONTINUOUS,
};
-static struct cyclecounter cyclecounter = {
+static struct cyclecounter cyclecounter __ro_after_init = {
.read = arch_counter_read_cc,
.mask = CLOCKSOURCE_MASK(56),
};
--
1.9.1
next reply other threads:[~2017-02-11 19:20 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-11 19:20 Bhumika Goyal [this message]
2017-02-11 20:31 ` Ard Biesheuvel
2017-02-11 20:36 ` Thomas Gleixner
2017-02-12 18:20 ` Bhumika Goyal
2017-02-12 18:56 ` Thomas Gleixner
2017-02-12 19:00 ` Bhumika Goyal
2017-02-12 20:07 ` Daniel Lezcano
2017-02-11 20:35 ` Thomas Gleixner
2017-02-12 18:21 ` Bhumika Goyal
2017-02-12 19:28 ` [tip:timers/core] clocksource/drivers/arm_arch_timer:: Mark cyclecounter __ro_after_init tip-bot for Bhumika Goyal
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=1486840818-22214-1-git-send-email-bhumirks@gmail.com \
--to=bhumirks@gmail.com \
--cc=daniel.lezcano@linaro.org \
--cc=julia.lawall@lip6.fr \
--cc=keescook@chromium.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marc.zyngier@arm.com \
--cc=mark.rutland@arm.com \
--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
Powered by JetHome