From: Heiko Stuebner <heiko@sntech.de>
To: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
Cc: Mike Turquette <mturquette@linaro.org>,
Stephen Boyd <sboyd@codeaurora.org>,
Sylwester Nawrocki <s.nawrocki@samsung.com>,
Tomasz Figa <tomasz.figa@gmail.com>,
Michal Simek <michal.simek@xilinx.com>,
kernel@pengutronix.de, linux-clk@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-rockchip@lists.infradead.org,
linux-samsung-soc@vger.kernel.org
Subject: Re: [PATCH] clk: make several parent names const
Date: Thu, 28 May 2015 12:35:12 +0200 [thread overview]
Message-ID: <4095482.AGzSOmiiYQ@phil> (raw)
In-Reply-To: <1432802751-6397-1-git-send-email-u.kleine-koenig@pengutronix.de>
Am Donnerstag, 28. Mai 2015, 10:45:51 schrieb Uwe Kleine-K=F6nig:
> Since commit 2893c379461a ("clk: make strings in parent name arrays
> const") the name of parent clocks can be const. So add more const in
> several clock drivers.
>=20
> Signed-off-by: Uwe Kleine-K=F6nig <u.kleine-koenig@pengutronix.de>
Acked-by: Heiko Stuebner <heiko@sntech.de>
> ---
> Hello,
>=20
> commit 2893c379461a isn't in Linus Torvald's tree yet, so the commit
> message needs adaption if clk-next is rewritten.
>=20
> Should I split this patch per subdir?
I don't have any Rockchip-related clock changes for 4.2, so for me it's=
not=20
important if you split it or keep it together.
Thanks
Heiko
WARNING: multiple messages have this Message-ID (diff)
From: Heiko Stuebner <heiko@sntech.de>
To: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
Cc: Mike Turquette <mturquette@linaro.org>,
Stephen Boyd <sboyd@codeaurora.org>,
Sylwester Nawrocki <s.nawrocki@samsung.com>,
Tomasz Figa <tomasz.figa@gmail.com>,
Michal Simek <michal.simek@xilinx.com>,
kernel@pengutronix.de, linux-clk@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-rockchip@lists.infradead.org,
linux-samsung-soc@vger.kernel.org
Subject: Re: [PATCH] clk: make several parent names const
Date: Thu, 28 May 2015 12:35:12 +0200 [thread overview]
Message-ID: <4095482.AGzSOmiiYQ@phil> (raw)
In-Reply-To: <1432802751-6397-1-git-send-email-u.kleine-koenig@pengutronix.de>
Am Donnerstag, 28. Mai 2015, 10:45:51 schrieb Uwe Kleine-König:
> Since commit 2893c379461a ("clk: make strings in parent name arrays
> const") the name of parent clocks can be const. So add more const in
> several clock drivers.
>
> Signed-off-by: Uwe Kleine-König <u.kleine-koenig@pengutronix.de>
Acked-by: Heiko Stuebner <heiko@sntech.de>
> ---
> Hello,
>
> commit 2893c379461a isn't in Linus Torvald's tree yet, so the commit
> message needs adaption if clk-next is rewritten.
>
> Should I split this patch per subdir?
I don't have any Rockchip-related clock changes for 4.2, so for me it's not
important if you split it or keep it together.
Thanks
Heiko
WARNING: multiple messages have this Message-ID (diff)
From: heiko@sntech.de (Heiko Stuebner)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] clk: make several parent names const
Date: Thu, 28 May 2015 12:35:12 +0200 [thread overview]
Message-ID: <4095482.AGzSOmiiYQ@phil> (raw)
In-Reply-To: <1432802751-6397-1-git-send-email-u.kleine-koenig@pengutronix.de>
Am Donnerstag, 28. Mai 2015, 10:45:51 schrieb Uwe Kleine-K?nig:
> Since commit 2893c379461a ("clk: make strings in parent name arrays
> const") the name of parent clocks can be const. So add more const in
> several clock drivers.
>
> Signed-off-by: Uwe Kleine-K?nig <u.kleine-koenig@pengutronix.de>
Acked-by: Heiko Stuebner <heiko@sntech.de>
> ---
> Hello,
>
> commit 2893c379461a isn't in Linus Torvald's tree yet, so the commit
> message needs adaption if clk-next is rewritten.
>
> Should I split this patch per subdir?
I don't have any Rockchip-related clock changes for 4.2, so for me it's not
important if you split it or keep it together.
Thanks
Heiko
next prev parent reply other threads:[~2015-05-28 10:35 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-28 8:45 [PATCH] clk: make several parent names const Uwe Kleine-König
2015-05-28 8:45 ` Uwe Kleine-König
2015-05-28 9:04 ` Sylwester Nawrocki
2015-05-28 9:04 ` Sylwester Nawrocki
2015-05-28 10:35 ` Heiko Stuebner [this message]
2015-05-28 10:35 ` Heiko Stuebner
2015-05-28 10:35 ` Heiko Stuebner
2015-06-04 21:27 ` Stephen Boyd
2015-06-04 21:27 ` Stephen Boyd
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=4095482.AGzSOmiiYQ@phil \
--to=heiko@sntech.de \
--cc=kernel@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=michal.simek@xilinx.com \
--cc=mturquette@linaro.org \
--cc=s.nawrocki@samsung.com \
--cc=sboyd@codeaurora.org \
--cc=tomasz.figa@gmail.com \
--cc=u.kleine-koenig@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 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.