From: p.zabel@pengutronix.de (Philipp Zabel)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/2] ARM: Make reset_control_ops const
Date: Thu, 25 Feb 2016 10:44:40 +0100 [thread overview]
Message-ID: <1456393482-26318-1-git-send-email-p.zabel@pengutronix.de> (raw)
Since commit 203d4f347d86 ("reset: Make reset_control_ops const") marked
the ops pointer in struct reset_controller_dev as const, these structs
can be made const, too. The commit is currently sitting in the
arm-soc/for-next branch.
regards
Philipp
Philipp Zabel (2):
ARM: imx: Make reset_control_ops const
ARM: sirf: Make reset_control_ops const
arch/arm/mach-imx/src.c | 2 +-
arch/arm/mach-prima2/rstc.c | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
--
2.7.0
next reply other threads:[~2016-02-25 9:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-25 9:44 Philipp Zabel [this message]
2016-02-25 9:44 ` [PATCH 1/2] ARM: imx: Make reset_control_ops const Philipp Zabel
2016-02-29 2:38 ` Shawn Guo
2016-02-25 9:44 ` [PATCH 2/2] ARM: sirf: " Philipp Zabel
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=1456393482-26318-1-git-send-email-p.zabel@pengutronix.de \
--to=p.zabel@pengutronix.de \
--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).