linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: "jay.xu@rock-chips.com" <jay.xu@rock-chips.com>
Cc: "Linus Walleij" <linus.walleij@linaro.org>,
	"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
	"Linux Next Mailing List" <linux-next@vger.kernel.org>
Subject: Re: linux-next: build failure after merge of the pinctrl tree
Date: Fri, 5 Mar 2021 13:12:52 +1100	[thread overview]
Message-ID: <20210305131252.649074fb@canb.auug.org.au> (raw)
In-Reply-To: <202103050846457413391@rock-chips.com>

[-- Attachment #1: Type: text/plain, Size: 1885 bytes --]

Hi,

On Fri, 5 Mar 2021 08:46:46 +0800 "jay.xu@rock-chips.com" <jay.xu@rock-chips.com> wrote:
>
> Thanks,and I think i have miss to upstream the changes,
> I have resend them in a new thread.
> 
> --- a/arch/arm64/Kconfig.platforms
> +++ b/arch/arm64/Kconfig.platforms
> @@ -155,9 +155,7 @@ config ARCH_REALTEK
>  config ARCH_ROCKCHIP
>         bool "Rockchip Platforms"
>         select ARCH_HAS_RESET_CONTROLLER
> -       select GPIOLIB
>         select PINCTRL
> -       select PINCTRL_ROCKCHIP
>         select PM
>         select ROCKCHIP_TIMER
>         help
> diff --git a/drivers/pinctrl/Kconfig b/drivers/pinctrl/Kconfig
> index b197d23324fb..970c18191f6f 100644
> --- a/drivers/pinctrl/Kconfig
> +++ b/drivers/pinctrl/Kconfig
> @@ -179,10 +179,14 @@ config PINCTRL_OXNAS
>  
>  config PINCTRL_ROCKCHIP
>         tristate "Rockchip gpio and pinctrl driver"
> +       select GPIOLIB
>         select PINMUX
>         select GENERIC_PINCONF
>         select GENERIC_IRQ_CHIP
>         select MFD_SYSCON
> +       default ARCH_ROCKCHIP
> +       help
> +         This support pinctrl and gpio driver for Rockchip SoCs.
>  
>  config PINCTRL_RZA1
>         bool "Renesas RZ/A1 gpio and pinctrl driver"
> 
> 
>  
> From: Linus Walleij
> Date: 2021-03-05 08:43
> To: jay.xu@rock-chips.com
> CC: Stephen Rothwell; Linux Kernel Mailing List; Linux Next Mailing List
> Subject: Re: Re: linux-next: build failure after merge of the pinctrl tree
> On Fri, Mar 5, 2021 at 1:13 AM jay.xu@rock-chips.com
> <jay.xu@rock-chips.com> wrote:
>  
> > Could you show me the issue log ?  
>  
> It's attached to Stephen's original mail in this thread.

Sorry I lost the error message, but it was a reference to a symbol that
has no EXPORT_SYMBOL.  So building the driver as a module should show
the error.

-- 
Cheers,
Stephen Rothwell

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

  parent reply	other threads:[~2021-03-05  2:13 UTC|newest]

Thread overview: 76+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-04  1:12 linux-next: build failure after merge of the pinctrl tree Stephen Rothwell
2021-03-04  8:16 ` Linus Walleij
2021-03-04  9:54   ` Stephen Rothwell
     [not found]   ` <202103050813501649431@rock-chips.com>
2021-03-05  0:43     ` Linus Walleij
     [not found]       ` <202103050846457413391@rock-chips.com>
2021-03-05  2:12         ` Stephen Rothwell [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-11-14  2:13 Stephen Rothwell
2023-11-14  7:46 ` Linus Walleij
2022-11-15  4:03 Stephen Rothwell
2022-11-10  4:09 Stephen Rothwell
2022-11-10  9:14 ` Linus Walleij
2022-11-09  2:46 Stephen Rothwell
2022-11-09  3:55 ` Yinbo Zhu
2022-11-09  8:31 ` Linus Walleij
2022-08-26  5:26 Stephen Rothwell
2022-08-26  8:01 ` Linus Walleij
2022-08-26 11:20   ` Wolfram Sang
2022-08-26 13:18     ` Linus Walleij
2022-09-12 13:40       ` Uwe Kleine-König
2022-08-02 22:21 broonie
2022-08-02 22:29 ` Mario Limonciello
2022-06-29  7:13 Stephen Rothwell
2022-06-27  6:01 Stephen Rothwell
2021-10-26  5:28 Stephen Rothwell
2021-10-26 12:30 ` Prathamesh Shete
2021-10-26 20:15   ` Linus Walleij
2021-10-26 21:21   ` Dmitry Osipenko
2021-10-28 12:31     ` Prathamesh Shete
2021-11-09  4:49       ` Linus Walleij
2021-01-27  9:41 Stephen Rothwell
2021-01-27 12:40 ` Krzysztof Kozlowski
2020-10-30  1:50 Stephen Rothwell
2020-11-04  3:10 ` Stephen Rothwell
2020-11-04 14:02   ` Linus Walleij
2020-07-17  7:16 Stephen Rothwell
2020-07-17  9:01 ` Hanks Chen
2020-07-17 11:37   ` Linus Walleij
2020-03-30  6:19 Stephen Rothwell
2020-02-25  1:21 Stephen Rothwell
2020-02-25  9:14 ` Marco Felsch
2019-08-21  6:16 Stephen Rothwell
2019-08-21  7:00 ` Linus Walleij
2016-12-06 22:27 Peter Rosin
2016-12-06 22:46 ` Stephen Rothwell
2016-12-06 23:05   ` Peter Rosin
2016-12-04 23:00 Stephen Rothwell
2016-12-06 21:31 ` Stephen Rothwell
2016-12-07 14:22   ` Linus Walleij
2016-05-12  4:14 Stephen Rothwell
2016-05-12 13:39 ` Linus Walleij
2015-12-21  4:58 Stephen Rothwell
2015-12-21  6:23 ` Pramod Kumar
2015-12-21  8:44 ` Linus Walleij
2015-12-18  3:45 Stephen Rothwell
2015-12-18  5:34 ` Pramod Kumar
2015-12-18  5:57   ` Stephen Rothwell
2015-12-18  6:12     ` Pramod Kumar
2015-12-18 17:05       ` Ray Jui
2015-09-25  3:34 Stephen Rothwell
2015-10-02  3:37 ` Stephen Rothwell
2015-10-05  7:38   ` Linus Walleij
2015-01-12  5:02 Stephen Rothwell
2015-01-12  7:25 ` Linus Walleij
2014-10-27  3:35 Stephen Rothwell
2014-05-30  6:08 Stephen Rothwell
2014-05-30  8:19 ` Linus Walleij
2014-02-11  3:56 Stephen Rothwell
2014-02-11  8:21 ` Linus Walleij
2013-12-10  3:02 Stephen Rothwell
2013-12-10  4:06 ` Stephen Rothwell
2013-12-10  8:50 ` Linus Walleij
2013-12-09  4:18 Stephen Rothwell
2013-09-20  3:27 Stephen Rothwell
2012-04-04  2:44 Stephen Rothwell
2012-04-04  3:43 ` Stephen Warren
2012-04-10  7:42   ` Linus Walleij
2012-04-10 15:12     ` Stephen Warren

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=20210305131252.649074fb@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=jay.xu@rock-chips.com \
    --cc=linus.walleij@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@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).