From: Axel Lin <axel.lin@ingics.com>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: Andreas Werner <andreas.werner@men.de>,
Alexandre Courbot <gnurou@gmail.com>,
linux-gpio@vger.kernel.org
Subject: [PATCH 2/2] gpio: menz127: Drop *mdev field from struct men_z127_gpio
Date: Wed, 09 Mar 2016 20:39:57 +0800 [thread overview]
Message-ID: <1457527197.720.2.camel@ingics.com> (raw)
In-Reply-To: <1457527135.720.1.camel@ingics.com>
No need to store *medv in struct men_z127_gpio.
Signed-off-by: Axel Lin <axel.lin@ingics.com>
---
drivers/gpio/gpio-menz127.c | 4 +---
1 file changed, 1 insertion(+), 3 deletions(-)
diff --git a/drivers/gpio/gpio-menz127.c b/drivers/gpio/gpio-menz127.c
index c5c9599..d979f4b 100644
--- a/drivers/gpio/gpio-menz127.c
+++ b/drivers/gpio/gpio-menz127.c
@@ -35,7 +35,6 @@
struct men_z127_gpio {
struct gpio_chip gc;
void __iomem *reg_base;
- struct mcb_device *mdev;
struct resource *mem;
};
@@ -43,7 +42,7 @@ static int men_z127_debounce(struct gpio_chip *gc, unsigned gpio,
unsigned debounce)
{
struct men_z127_gpio *priv = gpiochip_get_data(gc);
- struct device *dev = &priv->mdev->dev;
+ struct device *dev = gc->parent;
unsigned int rnd;
u32 db_en, db_cnt;
@@ -135,7 +134,6 @@ static int men_z127_probe(struct mcb_device *mdev,
goto err_release;
}
- men_z127_gpio->mdev = mdev;
mcb_set_drvdata(mdev, men_z127_gpio);
ret = bgpio_init(&men_z127_gpio->gc, &mdev->dev, 4,
--
2.1.4
next prev parent reply other threads:[~2016-03-09 12:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-09 12:38 [PATCH 1/2] gpio: menz127: Drop lock field from struct men_z127_gpio Axel Lin
2016-03-09 12:39 ` Axel Lin [this message]
2016-03-22 10:32 ` [PATCH 2/2] gpio: menz127: Drop *mdev " Linus Walleij
2016-03-22 10:31 ` [PATCH 1/2] gpio: menz127: Drop lock " Linus Walleij
2016-03-22 10:53 ` Axel Lin
2016-03-22 13:43 ` 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=1457527197.720.2.camel@ingics.com \
--to=axel.lin@ingics.com \
--cc=andreas.werner@men.de \
--cc=gnurou@gmail.com \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@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 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.