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>,
linux-gpio@vger.kernel.org,
Linus Walleij <linus.walleij@linaro.org>,
linux-arm-kernel@lists.infradead.org
Subject: Re: linux-next: Tree for Apr 16 (drivers/pinctrl/nomadik/pinctrl-abx500.c)
Date: Wed, 16 Apr 2025 14:47:14 -0700 [thread overview]
Message-ID: <f7af96df-4e64-4367-8dcf-416cef4019fc@infradead.org> (raw)
In-Reply-To: <20250416162556.3191a75e@canb.auug.org.au>
[-- Attachment #1: Type: text/plain, Size: 752 bytes --]
On 4/15/25 11:25 PM, Stephen Rothwell wrote:
> Hi all,
>
> News: there will be no linux-next releases this coming Friday or Monday
> or next Friday.
>
> Changes since 20250415:
>
on x86_64:
# CONFIG_OF is not set
../drivers/pinctrl/nomadik/pinctrl-abx500.c: In function 'abx500_dt_subnode_to_map':
../drivers/pinctrl/nomadik/pinctrl-abx500.c:776:15: error: implicit declaration of function 'pinconf_generic_parse_dt_config'; did you mean 'pinconf_generic_dump_config'? [-Wimplicit-function-declaration]
776 | ret = pinconf_generic_parse_dt_config(np, pctldev, &configs, &nconfigs);
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
| pinconf_generic_dump_config
Full randconfig file is attached.
--
~Randy
[-- Attachment #2: config-r8796.gz --]
[-- Type: application/gzip, Size: 46296 bytes --]
prev parent reply other threads:[~2025-04-16 21:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-16 6:25 linux-next: Tree for Apr 16 Stephen Rothwell
2025-04-16 19:01 ` linux-next: Tree for Apr 16 (pinctrl/abx500) Randy Dunlap
2025-04-16 21:08 ` linux-next: Tree for Apr 16 [drivers/gpu/drm/ttm/ttm.ko] Randy Dunlap
2025-04-16 21:40 ` linux-next: Tree for Apr 16 (drivers/gpu/drm/xe/xe_vsec.o) Randy Dunlap
2025-04-16 21: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=f7af96df-4e64-4367-8dcf-416cef4019fc@infradead.org \
--to=rdunlap@infradead.org \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.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