From: Matthias Brugger <matthias.bgg@gmail.com>
To: Philipp Zabel <p.zabel@pengutronix.de>,
Michael Turquette <mturquette@baylibre.com>
Cc: "Stephen Boyd" <sboyd@codeaurora.org>,
"Heiko Stuebner" <heiko@sntech.de>,
"Barry Song" <baohua@kernel.org>,
"Emilio López" <emilio@elopez.com.ar>,
"Maxime Ripard" <maxime.ripard@free-electrons.com>,
"Chen-Yu Tsai" <wens@csie.org>,
"Peter De Schrijver" <pdeschrijver@nvidia.com>,
"Prashant Gaikwad" <pgaikwad@nvidia.com>,
"Stephen Warren" <swarren@wwwdotorg.org>,
"Thierry Reding" <thierry.reding@gmail.com>,
"Alexandre Courbot" <gnurou@gmail.com>,
linux-clk@vger.kernel.org, kernel@pengutronix.de
Subject: Re: [PATCH 1/7] clk: mediatek: Make reset_control_ops const
Date: Thu, 25 Feb 2016 12:16:13 +0100 [thread overview]
Message-ID: <56CEE27D.1030206@gmail.com> (raw)
In-Reply-To: <1456393512-26602-2-git-send-email-p.zabel@pengutronix.de>
On 25/02/16 10:45, Philipp Zabel wrote:
> The mtk_reset_ops structure is never modified. Make it const.
>
> Signed-off-by: Philipp Zabel <p.zabel@pengutronix.de>
> ---
> drivers/clk/mediatek/reset.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/clk/mediatek/reset.c b/drivers/clk/mediatek/reset.c
> index 9e9fe4b..309049d 100644
> --- a/drivers/clk/mediatek/reset.c
> +++ b/drivers/clk/mediatek/reset.c
> @@ -57,7 +57,7 @@ static int mtk_reset(struct reset_controller_dev *rcdev,
> return mtk_reset_deassert(rcdev, id);
> }
>
> -static struct reset_control_ops mtk_reset_ops = {
> +static const struct reset_control_ops mtk_reset_ops = {
> .assert = mtk_reset_assert,
> .deassert = mtk_reset_deassert,
> .reset = mtk_reset,
>
Reviewed-by: Matthias Brugger <matthias.bgg@gmail.com>
next prev parent reply other threads:[~2016-02-25 11:16 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-25 9:45 [PATCH 0/7] clk: Make reset_control_ops const Philipp Zabel
2016-02-25 9:45 ` [PATCH 1/7] clk: mediatek: " Philipp Zabel
2016-02-25 11:16 ` Matthias Brugger [this message]
2016-03-29 23:29 ` Stephen Boyd
2016-02-25 9:45 ` [PATCH 2/7] clk: mmp: " Philipp Zabel
2016-03-29 23:29 ` Stephen Boyd
2016-02-25 9:45 ` [PATCH 3/7] clk: rockchip: " Philipp Zabel
2016-02-25 21:05 ` Heiko Stuebner
2016-03-29 23:29 ` Stephen Boyd
2016-02-25 9:45 ` [PATCH 4/7] clk: atlas7: " Philipp Zabel
2016-03-29 23:30 ` Stephen Boyd
2016-02-25 9:45 ` [PATCH 5/7] clk: sunxi: " Philipp Zabel
2016-03-29 23:30 ` Stephen Boyd
2016-02-25 9:45 ` [PATCH 6/7] clk: tegra: " Philipp Zabel
2016-03-29 23:30 ` Stephen Boyd
2016-02-25 9:45 ` [PATCH 7/7] clk: qcom: " Philipp Zabel
2016-03-29 23:30 ` Stephen Boyd
2016-02-25 21:04 ` [PATCH 0/7] clk: " Stephen Boyd
2016-02-26 8:24 ` Philipp Zabel
2016-03-04 18:55 ` Stephen Boyd
2016-03-07 9:55 ` 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=56CEE27D.1030206@gmail.com \
--to=matthias.bgg@gmail.com \
--cc=baohua@kernel.org \
--cc=emilio@elopez.com.ar \
--cc=gnurou@gmail.com \
--cc=heiko@sntech.de \
--cc=kernel@pengutronix.de \
--cc=linux-clk@vger.kernel.org \
--cc=maxime.ripard@free-electrons.com \
--cc=mturquette@baylibre.com \
--cc=p.zabel@pengutronix.de \
--cc=pdeschrijver@nvidia.com \
--cc=pgaikwad@nvidia.com \
--cc=sboyd@codeaurora.org \
--cc=swarren@wwwdotorg.org \
--cc=thierry.reding@gmail.com \
--cc=wens@csie.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.