From: Abel Vesa <abel.vesa@nxp.com>
To: Stephen Boyd <sboyd@kernel.org>, Shawn Guo <shawnguo@kernel.org>,
Sascha Hauer <kernel@pengutronix.de>,
Aisheng Dong <aisheng.dong@nxp.com>
Cc: "linux-clk@vger.kernel.org" <linux-clk@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
dl-linux-imx <linux-imx@nxp.com>, Abel Vesa <abel.vesa@nxp.com>
Subject: [PATCH 0/3] clk: imx: Make all the parent_names arrays be const pointers
Date: Fri, 14 Dec 2018 15:30:08 +0000 [thread overview]
Message-ID: <1544801400-18951-1-git-send-email-abel.vesa@nxp.com> (raw)
This is mainly to shut up the checkpatch.pl script warnings about the
"static const char *" needing to be "static const char * const".
Abel Vesa (3):
clk: imx: Make parent_names const pointer in composite-8m
clk: imx: Make parents const pointer in mux wrappers
clk: imx8mq: Make parent names arrays const pointers
drivers/clk/imx/clk-composite-8m.c | 2 +-
drivers/clk/imx/clk-imx8mq.c | 194 ++++++++++++++++++-------------------
drivers/clk/imx/clk.h | 5 +-
3 files changed, 101 insertions(+), 100 deletions(-)
--
2.7.4
next reply other threads:[~2018-12-14 15:30 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-14 15:30 Abel Vesa [this message]
2018-12-14 15:30 ` [PATCH 1/3] clk: imx: Make parent_names const pointer in composite-8m Abel Vesa
2019-01-09 19:02 ` Stephen Boyd
2018-12-14 15:30 ` [PATCH 2/3] clk: imx: Make parents const pointer in mux wrappers Abel Vesa
2019-01-09 19:02 ` Stephen Boyd
2018-12-14 15:30 ` [PATCH 3/3] clk: imx8mq: Make parent names arrays const pointers Abel Vesa
2019-01-09 19:02 ` Stephen Boyd
2018-12-14 21:08 ` [PATCH 0/3] clk: imx: Make all the parent_names arrays be " Stephen Boyd
2018-12-17 11:35 ` Abel Vesa
2018-12-17 18:40 ` Stephen Boyd
2018-12-17 18:59 ` Abel Vesa
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=1544801400-18951-1-git-send-email-abel.vesa@nxp.com \
--to=abel.vesa@nxp.com \
--cc=aisheng.dong@nxp.com \
--cc=kernel@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-imx@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sboyd@kernel.org \
--cc=shawnguo@kernel.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).