From: arvind.yadav.cs@gmail.com (Arvind Yadav)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/9] coresight: constify amba_id
Date: Thu, 24 Aug 2017 22:05:57 +0530 [thread overview]
Message-ID: <1503592565-21601-2-git-send-email-arvind.yadav.cs@gmail.com> (raw)
In-Reply-To: <1503592565-21601-1-git-send-email-arvind.yadav.cs@gmail.com>
amba_id are not supposed to change at runtime. All functions
working with const amba_id. So mark the non-const structs as const.
Signed-off-by: Arvind Yadav <arvind.yadav.cs@gmail.com>
---
drivers/hwtracing/coresight/coresight-cpu-debug.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/hwtracing/coresight/coresight-cpu-debug.c b/drivers/hwtracing/coresight/coresight-cpu-debug.c
index 64a77e0..6ea62c6 100644
--- a/drivers/hwtracing/coresight/coresight-cpu-debug.c
+++ b/drivers/hwtracing/coresight/coresight-cpu-debug.c
@@ -667,7 +667,7 @@ static int debug_remove(struct amba_device *adev)
return 0;
}
-static struct amba_id debug_ids[] = {
+static const struct amba_id debug_ids[] = {
{ /* Debug for Cortex-A53 */
.id = 0x000bbd03,
.mask = 0x000fffff,
--
2.7.4
next prev parent reply other threads:[~2017-08-24 16:35 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-24 16:35 [PATCH 0/9] constify amba_id Arvind Yadav
2017-08-24 16:35 ` Arvind Yadav [this message]
2017-08-24 16:35 ` [PATCH 2/9] coresight: etb10: " Arvind Yadav
2017-08-24 16:35 ` [PATCH 3/9] coresight: etm3x: " Arvind Yadav
2017-08-24 16:36 ` [PATCH 4/9] coresight: etm4x: " Arvind Yadav
2017-08-24 16:36 ` [PATCH 5/9] coresight: funnel: " Arvind Yadav
2017-08-24 16:36 ` [PATCH 6/9] coresight: replicator: " Arvind Yadav
2017-08-24 16:36 ` [PATCH 7/9] coresight: stm: " Arvind Yadav
2017-08-24 16:36 ` [PATCH 8/9] coresight: tmc: " Arvind Yadav
2017-08-24 16:36 ` [PATCH 9/9] coresight: tpiu: " Arvind Yadav
2017-08-25 16:20 ` [PATCH 0/9] " Mathieu Poirier
2017-08-25 17:59 ` arvind
2017-08-28 16:48 ` Mathieu Poirier
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=1503592565-21601-2-git-send-email-arvind.yadav.cs@gmail.com \
--to=arvind.yadav.cs@gmail.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).