From: "Jonathan Neuschäfer" <j.neuschaefer@gmx.net>
To: linux-clk@vger.kernel.org
Cc: linux-kernel@vger.kernel.org,
"Jonathan Neuschäfer" <j.neuschaefer@gmx.net>
Subject: [PATCH 0/5] clk: Declare mux tables as const u32[]
Date: Sat, 29 Jan 2022 10:51:53 +0100 [thread overview]
Message-ID: <20220129095159.2202366-1-j.neuschaefer@gmx.net> (raw)
I noticed that the 'table' parameter to clk_register_mux_table is never
used for modifying the table elements, and so it can be declared const.
Jonathan Neuschäfer (5):
clk: mux: Declare u32 *table parameter as const
clk: hisilicon: Remove unnecessary cast of mux table to u32 *
clk: mmp: Declare mux tables as const u32[]
clk: qcom: Declare mux table as const u32[]
clk: pistachio: Declare mux table as const u32[]
drivers/clk/clk-mux.c | 10 +++++-----
drivers/clk/hisilicon/clk.c | 2 +-
drivers/clk/mmp/clk-of-mmp2.c | 4 ++--
drivers/clk/pistachio/clk-pistachio.c | 2 +-
drivers/clk/qcom/kpss-xcc.c | 2 +-
include/linux/clk-provider.h | 12 ++++++------
6 files changed, 16 insertions(+), 16 deletions(-)
--
2.34.1
next reply other threads:[~2022-01-29 9:52 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-29 9:51 Jonathan Neuschäfer [this message]
2022-01-29 9:51 ` [PATCH 1/5] clk: mux: Declare u32 *table parameter as const Jonathan Neuschäfer
2022-01-31 3:44 ` kernel test robot
2022-01-31 14:45 ` Jonathan Neuschäfer
2022-01-31 4:15 ` kernel test robot
2022-01-29 9:51 ` [PATCH 2/5] clk: hisilicon: Remove unnecessary cast of mux table to u32 * Jonathan Neuschäfer
2022-01-29 9:51 ` [PATCH 3/5] clk: mmp: Declare mux tables as const u32[] Jonathan Neuschäfer
2022-01-29 9:51 ` [PATCH 4/5] clk: qcom: Declare mux table " Jonathan Neuschäfer
2022-01-29 9:51 ` [PATCH 5/5] clk: pistachio: " Jonathan Neuschäfer
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=20220129095159.2202366-1-j.neuschaefer@gmx.net \
--to=j.neuschaefer@gmx.net \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.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
all inboxes | Powered by JetHome®