From: "Tanwar, Rahul" <rahul.tanwar@linux.intel.com>
To: Randy Dunlap <rdunlap@infradead.org>,
Stephen Rothwell <sfr@canb.auug.org.au>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linus Walleij <linus.walleij@linaro.org>,
"linux-gpio@vger.kernel.org" <linux-gpio@vger.kernel.org>
Subject: Re: linux-next: Tree for Dec 3 (pinctrl-equilibrium)
Date: Wed, 4 Dec 2019 17:36:39 +0800 [thread overview]
Message-ID: <1c54235b-545c-db3e-4225-ec6824ac6003@linux.intel.com> (raw)
In-Reply-To: <1a78124d-bef9-46da-aef4-60f85fddfceb@infradead.org>
Hi Randy,
On 4/12/2019 12:33 AM, Randy Dunlap wrote:
> On 12/2/19 8:54 PM, Stephen Rothwell wrote:
>> Hi all,
>>
>> Please do not add any material for v5.6 to your linux-next included
>> trees until after v5.5-rc1 has been released.
>>
>> Changes since 20191202:
>>
> on x86_64:
> # CONFIG_OF is not set
>
>
> ld: drivers/pinctrl/pinctrl-equilibrium.o: in function `pinconf_generic_dt_node_to_map_all':
> pinctrl-equilibrium.c:(.text+0xb): undefined reference to `pinconf_generic_dt_node_to_map'
>
> Probably depends on OF.
Can you please tell the compiler/toolchain details that you used when you see
above error ?I tried few versions of gcc and i never see this linker error.
Build always passed successfully.
I have a patch that adds 'depends on OF' in the Kconfig to resolve this but i
want to ensure that i recreate this error first & confirm resolution with the
patch before posting it. Thanks.
Regards,
Rahul
next prev parent reply other threads:[~2019-12-04 9:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20191203155405.31404722@canb.auug.org.au>
2019-12-03 16:33 ` linux-next: Tree for Dec 3 (pinctrl-equilibrium) Randy Dunlap
2019-12-04 9:36 ` Tanwar, Rahul [this message]
2019-12-04 16:04 ` Randy Dunlap
2019-12-04 23:36 ` 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=1c54235b-545c-db3e-4225-ec6824ac6003@linux.intel.com \
--to=rahul.tanwar@linux.intel.com \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=rdunlap@infradead.org \
--cc=sfr@canb.auug.org.au \
/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).