From: Stephen Boyd <sboyd@codeaurora.org>
To: Philipp Zabel <p.zabel@pengutronix.de>
Cc: "Michael Turquette" <mturquette@baylibre.com>,
"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>,
"Matthias Brugger" <matthias.bgg@gmail.com>,
linux-clk@vger.kernel.org, kernel@pengutronix.de
Subject: Re: [PATCH 0/7] clk: Make reset_control_ops const
Date: Thu, 25 Feb 2016 13:04:39 -0800 [thread overview]
Message-ID: <20160225210439.GI4847@codeaurora.org> (raw)
In-Reply-To: <1456393512-26602-1-git-send-email-p.zabel@pengutronix.de>
On 02/25, Philipp Zabel wrote:
> 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.
>
All these patches look fine. I take it we have to wait for a
cycle to merge them though because the commit you mention is only
in the arm-soc tree? Or did you want to take them through arm-soc?
--
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundation Collaborative Project
next prev parent reply other threads:[~2016-02-25 21:04 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
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 ` Stephen Boyd [this message]
2016-02-26 8:24 ` [PATCH 0/7] clk: " 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=20160225210439.GI4847@codeaurora.org \
--to=sboyd@codeaurora.org \
--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=matthias.bgg@gmail.com \
--cc=maxime.ripard@free-electrons.com \
--cc=mturquette@baylibre.com \
--cc=p.zabel@pengutronix.de \
--cc=pdeschrijver@nvidia.com \
--cc=pgaikwad@nvidia.com \
--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 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).