From: Ralph Sennhauser <ralph.sennhauser@gmail.com>
To: linux-gpio@vger.kernel.org
Cc: Ralph Sennhauser <ralph.sennhauser@gmail.com>,
Linus Walleij <linus.walleij@linaro.org>,
Alexandre Courbot <gnurou@gmail.com>,
open list <linux-kernel@vger.kernel.org>
Subject: [PATCH 6/6] gpio: mvebu: let the compiler inline
Date: Thu, 16 Mar 2017 07:34:01 +0100 [thread overview]
Message-ID: <20170316063402.8667-7-ralph.sennhauser@gmail.com> (raw)
In-Reply-To: <20170316063402.8667-1-ralph.sennhauser@gmail.com>
A modern compiler should know better when to inline, so drop the inline
keywords.
Signed-off-by: Ralph Sennhauser <ralph.sennhauser@gmail.com>
---
drivers/gpio/gpio-mvebu.c | 18 +++++++-----------
1 file changed, 7 insertions(+), 11 deletions(-)
diff --git a/drivers/gpio/gpio-mvebu.c b/drivers/gpio/gpio-mvebu.c
index d9aa77b..029f43c 100644
--- a/drivers/gpio/gpio-mvebu.c
+++ b/drivers/gpio/gpio-mvebu.c
@@ -99,35 +99,32 @@ struct mvebu_gpio_chip {
* Functions returning addresses of individual registers for a given
* GPIO controller.
*/
-static inline void __iomem *mvebu_gpioreg_out(struct mvebu_gpio_chip *mvchip)
+static void __iomem *mvebu_gpioreg_out(struct mvebu_gpio_chip *mvchip)
{
return mvchip->membase + GPIO_OUT_OFF;
}
-static inline void __iomem *mvebu_gpioreg_blink(struct mvebu_gpio_chip *mvchip)
+static void __iomem *mvebu_gpioreg_blink(struct mvebu_gpio_chip *mvchip)
{
return mvchip->membase + GPIO_BLINK_EN_OFF;
}
-static inline void __iomem *
-mvebu_gpioreg_io_conf(struct mvebu_gpio_chip *mvchip)
+static void __iomem *mvebu_gpioreg_io_conf(struct mvebu_gpio_chip *mvchip)
{
return mvchip->membase + GPIO_IO_CONF_OFF;
}
-static inline void __iomem *mvebu_gpioreg_in_pol(struct mvebu_gpio_chip *mvchip)
+static void __iomem *mvebu_gpioreg_in_pol(struct mvebu_gpio_chip *mvchip)
{
return mvchip->membase + GPIO_IN_POL_OFF;
}
-static inline void __iomem *
-mvebu_gpioreg_data_in(struct mvebu_gpio_chip *mvchip)
+static void __iomem *mvebu_gpioreg_data_in(struct mvebu_gpio_chip *mvchip)
{
return mvchip->membase + GPIO_DATA_IN_OFF;
}
-static inline void __iomem *
-mvebu_gpioreg_edge_cause(struct mvebu_gpio_chip *mvchip)
+static void __iomem *mvebu_gpioreg_edge_cause(struct mvebu_gpio_chip *mvchip)
{
int cpu;
@@ -144,8 +141,7 @@ mvebu_gpioreg_edge_cause(struct mvebu_gpio_chip *mvchip)
}
}
-static inline void __iomem *
-mvebu_gpioreg_edge_mask(struct mvebu_gpio_chip *mvchip)
+static void __iomem *mvebu_gpioreg_edge_mask(struct mvebu_gpio_chip *mvchip)
{
int cpu;
--
2.10.2
next prev parent reply other threads:[~2017-03-16 6:34 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-16 6:33 [PATCH 0/6] gpio: mvebu: prepatatory cleanup for pwm-fan support Ralph Sennhauser
2017-03-16 6:33 ` [PATCH 1/6] gpio: mvebu: checkpatch: block comment fixes Ralph Sennhauser
2017-03-16 15:40 ` Linus Walleij
2017-03-16 6:33 ` [PATCH 2/6] gpio: mvebu: start multiline block comments with blank line Ralph Sennhauser
2017-03-16 15:41 ` Linus Walleij
2017-03-16 6:33 ` [PATCH 3/6] gpio: mvebu: checkpatch: unsigned int fixes Ralph Sennhauser
2017-03-16 15:42 ` Linus Walleij
2017-03-16 6:33 ` [PATCH 4/6] gpio: mvebu: checkpatch: whitespace fixes Ralph Sennhauser
2017-03-16 15:42 ` Linus Walleij
2017-03-16 6:34 ` [PATCH 5/6] gpio: mvebu: extra " Ralph Sennhauser
2017-03-16 15:43 ` Linus Walleij
2017-03-16 6:34 ` Ralph Sennhauser [this message]
2017-03-16 15:44 ` [PATCH 6/6] gpio: mvebu: let the compiler inline Linus Walleij
2017-03-17 9:08 ` Ralph Sennhauser
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=20170316063402.8667-7-ralph.sennhauser@gmail.com \
--to=ralph.sennhauser@gmail.com \
--cc=gnurou@gmail.com \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@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;
as well as URLs for NNTP newsgroup(s).