From: Shawn Guo <shawnguo@kernel.org>
To: Dan Carpenter <dan.carpenter@oracle.com>
Cc: Linus Walleij <linus.walleij@linaro.org>,
Baoyou Xie <xie.baoyou@sanechips.com.cn>,
Xin Zhou <zhou.xin8@sanechips.com.cn>,
Jun Nie <jun.nie@linaro.org>,
linux-gpio@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
Shawn Guo <shawn.guo@linaro.org>
Subject: Re: [PATCH] pinctrl: zte: fix 'functions' allocation in zx_pinctrl_build_state()
Date: Mon, 17 Jul 2017 17:46:24 +0800 [thread overview]
Message-ID: <20170717094622.GE3172@dragon> (raw)
In-Reply-To: <20170717080221.gqf7xgeo2zqgigdq@mwanda>
On Mon, Jul 17, 2017 at 11:02:21AM +0300, Dan Carpenter wrote:
> Shouldn't there be a free if the remove function? I'm not even sure
> where the remove function is so I don't know.
As the pinctrl driver is essential for the platform, it's always a
builtin_platform_driver which we do not even have a remove function.
Shawn
WARNING: multiple messages have this Message-ID (diff)
From: shawnguo@kernel.org (Shawn Guo)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] pinctrl: zte: fix 'functions' allocation in zx_pinctrl_build_state()
Date: Mon, 17 Jul 2017 17:46:24 +0800 [thread overview]
Message-ID: <20170717094622.GE3172@dragon> (raw)
In-Reply-To: <20170717080221.gqf7xgeo2zqgigdq@mwanda>
On Mon, Jul 17, 2017 at 11:02:21AM +0300, Dan Carpenter wrote:
> Shouldn't there be a free if the remove function? I'm not even sure
> where the remove function is so I don't know.
As the pinctrl driver is essential for the platform, it's always a
builtin_platform_driver which we do not even have a remove function.
Shawn
next prev parent reply other threads:[~2017-07-17 9:46 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-16 13:33 [PATCH] pinctrl: zte: fix 'functions' allocation in zx_pinctrl_build_state() Shawn Guo
2017-07-16 13:33 ` Shawn Guo
2017-07-17 8:02 ` Dan Carpenter
2017-07-17 8:02 ` Dan Carpenter
2017-07-17 9:46 ` Shawn Guo [this message]
2017-07-17 9:46 ` Shawn Guo
2017-07-17 9:55 ` Dan Carpenter
2017-07-17 9:55 ` Dan Carpenter
2017-08-02 8:31 ` Linus Walleij
2017-08-02 8:31 ` 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=20170717094622.GE3172@dragon \
--to=shawnguo@kernel.org \
--cc=dan.carpenter@oracle.com \
--cc=jun.nie@linaro.org \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-gpio@vger.kernel.org \
--cc=shawn.guo@linaro.org \
--cc=xie.baoyou@sanechips.com.cn \
--cc=zhou.xin8@sanechips.com.cn \
/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.