From: Antoine Tenart <antoine.tenart@free-electrons.com>
To: Philipp Zabel <p.zabel@pengutronix.de>
Cc: linux-kernel@vger.kernel.org,
Antoine Tenart <antoine.tenart@free-electrons.com>
Subject: Re: [PATCH] reset: berlin: Make reset_control_ops const
Date: Mon, 8 Feb 2016 14:34:55 +0100 [thread overview]
Message-ID: <20160208133455.GE4117@kwain> (raw)
In-Reply-To: <1454938100-8527-1-git-send-email-p.zabel@pengutronix.de>
[-- Attachment #1: Type: text/plain, Size: 962 bytes --]
On Mon, Feb 08, 2016 at 02:28:20PM +0100, Philipp Zabel wrote:
> The berlin_reset_ops structure is never modified. Make it const.
>
> Signed-off-by: Philipp Zabel <p.zabel@pengutronix.de>
Acked-by: Antoine Tenart <antoine.tenart@free-electrons.com>
> ---
> drivers/reset/reset-berlin.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/reset/reset-berlin.c b/drivers/reset/reset-berlin.c
> index ac017df..369f391 100644
> --- a/drivers/reset/reset-berlin.c
> +++ b/drivers/reset/reset-berlin.c
> @@ -46,7 +46,7 @@ static int berlin_reset_reset(struct reset_controller_dev *rcdev,
> return 0;
> }
>
> -static struct reset_control_ops berlin_reset_ops = {
> +static const struct reset_control_ops berlin_reset_ops = {
> .reset = berlin_reset_reset,
> };
>
> --
> 2.7.0.rc3
>
--
Antoine Ténart, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2016-02-08 13:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-08 13:28 [PATCH] reset: berlin: Make reset_control_ops const Philipp Zabel
2016-02-08 13:34 ` Antoine Tenart [this message]
2016-02-08 14:57 ` kbuild test robot
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=20160208133455.GE4117@kwain \
--to=antoine.tenart@free-electrons.com \
--cc=linux-kernel@vger.kernel.org \
--cc=p.zabel@pengutronix.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).