From: Linus Walleij <linus.walleij@linaro.org>
To: Jianqun Xu <jay.xu@rock-chips.com>
Cc: "Heiko Stübner" <heiko@sntech.de>,
"Catalin Marinas" <catalin.marinas@arm.com>,
"Will Deacon" <will@kernel.org>,
"open list:GPIO SUBSYSTEM" <linux-gpio@vger.kernel.org>,
"open list:ARM/Rockchip SoC..."
<linux-rockchip@lists.infradead.org>
Subject: Re: [PATCH 0/2] make rockchip pinctrl module able
Date: Wed, 10 Mar 2021 23:57:36 +0100 [thread overview]
Message-ID: <CACRpkdYcKPehB2ugpDsD+mZ81eOey7ciK76BEJT_wECH_O1zGQ@mail.gmail.com> (raw)
In-Reply-To: <20210305003907.1692515-1-jay.xu@rock-chips.com>
On Fri, Mar 5, 2021 at 1:39 AM Jianqun Xu <jay.xu@rock-chips.com> wrote:
> Make the rockchip pinctrl driver able to be module by unselect
> PINCTRL_ROCKCHIP from ARCH_ROCKCHIP, then modify driver module define.
This patch set fails like this:
ERROR: modpost: "irq_gc_set_wake"
[drivers/pinctrl/pinctrl-rockchip.ko] undefined!
make[3]: *** [../scripts/Makefile.modpost:132: Module.symvers] Error 1
make[3]: *** Deleting file 'Module.symvers'
make[2]: *** [/home/linus/linux-pinctrl/Makefile:1440: modules] Error 2
Probably this function needs to get exported. (Send a separate
patch for that.)
Yours,
Linus Walleij
Yours,
Linus Walleij
_______________________________________________
Linux-rockchip mailing list
Linux-rockchip@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-rockchip
next prev parent reply other threads:[~2021-03-10 22:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-05 0:39 [PATCH 0/2] make rockchip pinctrl module able Jianqun Xu
2021-03-05 0:39 ` [PATCH 1/2] arm64: remove select PINCTRL_ROCKCHIP from ARCH_ROCKCHIP Jianqun Xu
2021-03-22 0:03 ` jay.xu
2021-03-05 0:39 ` [PATCH 2/2] pinctrl: rockchip: make driver be tristate module Jianqun Xu
2021-03-10 22:57 ` Linus Walleij [this message]
2021-03-15 15:32 ` [PATCH 0/2] make rockchip pinctrl module able Linus Walleij
2021-03-16 0:07 ` jay.xu
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=CACRpkdYcKPehB2ugpDsD+mZ81eOey7ciK76BEJT_wECH_O1zGQ@mail.gmail.com \
--to=linus.walleij@linaro.org \
--cc=catalin.marinas@arm.com \
--cc=heiko@sntech.de \
--cc=jay.xu@rock-chips.com \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=will@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).