From: Rikard Falkeborn <rikard.falkeborn@gmail.com>
To: "Andreas Färber" <afaerber@suse.de>,
"Manivannan Sadhasivam" <manivannan.sadhasivam@linaro.org>,
"Linus Walleij" <linus.walleij@linaro.org>
Cc: linux-arm-kernel@lists.infradead.org, linux-gpio@vger.kernel.org,
linux-kernel@vger.kernel.org,
Rikard Falkeborn <rikard.falkeborn@gmail.com>
Subject: [PATCH 0/3] pinctrl/actions: Constify static variables
Date: Mon, 31 Aug 2020 00:43:08 +0200 [thread overview]
Message-ID: <20200830224311.36994-1-rikard.falkeborn@gmail.com> (raw)
Constify a couple of static variables which are not modified to allow
the compiler to put them in read-only memory. Patch 1/3 is probably
the most important one since those structs contain function pointer.
The patches are independent, and can be applied in any order.
Compile-tested only.
Rikard Falkeborn (3):
pinctrl: actions: pinctrl-owl: Constify owl_pinctrl_ops and
owl_pinmux_ops
pinctrl: actions: pinctrl-s700: Constify s700_padinfo[]
pinctrl: actions: pinctrl-s900: Constify s900_padinfo[]
drivers/pinctrl/actions/pinctrl-owl.c | 4 ++--
drivers/pinctrl/actions/pinctrl-s700.c | 2 +-
drivers/pinctrl/actions/pinctrl-s900.c | 2 +-
3 files changed, 4 insertions(+), 4 deletions(-)
--
2.28.0
next reply other threads:[~2020-08-30 22:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-30 22:43 Rikard Falkeborn [this message]
2020-08-30 22:43 ` [PATCH 1/3] pinctrl: actions: pinctrl-owl: Constify owl_pinctrl_ops and owl_pinmux_ops Rikard Falkeborn
2020-08-30 22:43 ` [PATCH 2/3] pinctrl: actions: pinctrl-s700: Constify s700_padinfo[] Rikard Falkeborn
2020-08-30 22:43 ` [PATCH 3/3] pinctrl: actions: pinctrl-s900: Constify s900_padinfo[] Rikard Falkeborn
2020-08-31 9:15 ` [PATCH 0/3] pinctrl/actions: Constify static variables Manivannan Sadhasivam
2020-09-12 10:15 ` Linus Walleij
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=20200830224311.36994-1-rikard.falkeborn@gmail.com \
--to=rikard.falkeborn@gmail.com \
--cc=afaerber@suse.de \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=manivannan.sadhasivam@linaro.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®