From: Randy Dunlap <rdunlap@infradead.org>
To: 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 Mar 30 (drivers/pinctrl/bcm/pinctrl-bcm63[256]8.o)
Date: Tue, 30 Mar 2021 09:47:30 -0700 [thread overview]
Message-ID: <abc7d372-e561-ea6c-f078-30d936db6b06@infradead.org> (raw)
In-Reply-To: <20210330192729.317ff70e@canb.auug.org.au>
[-- Attachment #1: Type: text/plain, Size: 850 bytes --]
On 3/30/21 1:27 AM, Stephen Rothwell wrote:
> Hi all,
>
> News: there will be no linux-next release on Friday or the following
> Monday.
>
> Changes since 20210329:
>
on x86_64:
# CONFIG_OF is not set
ld: drivers/pinctrl/bcm/pinctrl-bcm6328.o: in function `pinconf_generic_dt_node_to_map_pin':
pinctrl-bcm6328.c:(.text+0x13f): undefined reference to `pinconf_generic_dt_node_to_map'
ld: drivers/pinctrl/bcm/pinctrl-bcm6358.o: in function `pinconf_generic_dt_node_to_map_pin':
pinctrl-bcm6358.c:(.text+0x2ff): undefined reference to `pinconf_generic_dt_node_to_map'
ld: drivers/pinctrl/bcm/pinctrl-bcm6368.o: in function `pinconf_generic_dt_node_to_map_pin':
pinctrl-bcm6368.c:(.text+0x3ff): undefined reference to `pinconf_generic_dt_node_to_map'
Full randconfig file is attached.
--
~Randy
Reported-by: Randy Dunlap <rdunlap@infradead.org>
[-- Attachment #2: config-r8530.gz --]
[-- Type: application/gzip, Size: 27631 bytes --]
prev parent reply other threads:[~2021-03-30 16:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-30 8:27 linux-next: Tree for Mar 30 Stephen Rothwell
2021-03-30 16:47 ` Randy Dunlap [this message]
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=abc7d372-e561-ea6c-f078-30d936db6b06@infradead.org \
--to=rdunlap@infradead.org \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.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).