From: Matthias Brugger <matthias.bgg@gmail.com>
To: light.hsieh@mediatek.com, linus.walleij@linaro.org
Cc: sean.wang@kernel.org, kuohong.wang@mediatek.com,
linux-kernel@vger.kernel.org, linux-gpio@vger.kernel.org,
linux-mediatek@lists.infradead.org
Subject: Re: [PATCH v1 2/2] pinctrl: make MediaTek MT6765 pinctrl ready for buidling loadable module
Date: Tue, 18 Feb 2020 17:40:10 +0100 [thread overview]
Message-ID: <dbe41adb-356e-a5c7-99de-c98850f8cd90@gmail.com> (raw)
In-Reply-To: <1582016614-20728-2-git-send-email-light.hsieh@mediatek.com>
On 18/02/2020 10:03, light.hsieh@mediatek.com wrote:
> From: Light Hsieh <light.hsieh@mediatek.com>
>
> This patch make pinctrl-mt6765 ready for building as
> loadable module.
>
> Signed-off-by: Light Hsieh <light.hsieh@mediatek.com>
Reviewed-by: Matthias Brugger <matthias.bgg@gmail.com>
> ---
> drivers/pinctrl/mediatek/Kconfig | 2 +-
> drivers/pinctrl/mediatek/pinctrl-mt6765.c | 4 ++++
> 2 files changed, 5 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/pinctrl/mediatek/Kconfig b/drivers/pinctrl/mediatek/Kconfig
> index 4cd1109..c645fdb 100644
> --- a/drivers/pinctrl/mediatek/Kconfig
> +++ b/drivers/pinctrl/mediatek/Kconfig
> @@ -89,7 +89,7 @@ config PINCTRL_MT2712
> select PINCTRL_MTK
>
> config PINCTRL_MT6765
> - bool "Mediatek MT6765 pin control"
> + tristate "Mediatek MT6765 pin control"
> depends on OF
> depends on ARM64 || COMPILE_TEST
> default ARM64 && ARCH_MEDIATEK
> diff --git a/drivers/pinctrl/mediatek/pinctrl-mt6765.c b/drivers/pinctrl/mediatek/pinctrl-mt6765.c
> index 905dae8c..2c59d39 100644
> --- a/drivers/pinctrl/mediatek/pinctrl-mt6765.c
> +++ b/drivers/pinctrl/mediatek/pinctrl-mt6765.c
> @@ -6,6 +6,7 @@
> *
> */
>
> +#include <linux/module.h>
> #include "pinctrl-mtk-mt6765.h"
> #include "pinctrl-paris.h"
>
> @@ -1103,3 +1104,6 @@ static int __init mt6765_pinctrl_init(void)
> return platform_driver_register(&mt6765_pinctrl_driver);
> }
> arch_initcall(mt6765_pinctrl_init);
> +
> +MODULE_LICENSE("GPL v2");
> +MODULE_DESCRIPTION("MediaTek MT6765 Pinctrl Driver");
>
next prev parent reply other threads:[~2020-02-18 16:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-18 9:03 [PATCH v1 1/2] pinctrl: make MediaTek pinctrl v2 driver " light.hsieh
2020-02-18 9:03 ` [PATCH v1 2/2] pinctrl: make MediaTek MT6765 pinctrl " light.hsieh
2020-02-18 16:40 ` Matthias Brugger [this message]
2020-02-18 16:39 ` [PATCH v1 1/2] pinctrl: make MediaTek pinctrl v2 driver " Matthias Brugger
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=dbe41adb-356e-a5c7-99de-c98850f8cd90@gmail.com \
--to=matthias.bgg@gmail.com \
--cc=kuohong.wang@mediatek.com \
--cc=light.hsieh@mediatek.com \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=sean.wang@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®