From: Peter Hurley <peter-WaGBZJeGNqdsbIuE7sb01tBPR1lH4CV8@public.gmane.org>
To: Greg Kroah-Hartman
<gregkh-hQyY1W1yCW8ekmWlsbkhG0B+6BGkLq7r@public.gmane.org>
Cc: kbuild test robot
<fengguang.wu-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>,
kbuild-all-JC7UmRfGjtg@public.gmane.org,
Rob Herring <robh+dt-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>,
Grant Likely
<grant.likely-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>,
"devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: [tty:tty-testing 9/30] drivers/of/fdt.c:807:2: error: implicit declaration of function 'fdt_path_offset_namelen'
Date: Tue, 28 Apr 2015 09:26:05 -0400 [thread overview]
Message-ID: <553F8A6D.9040404@hurleysoftware.com> (raw)
In-Reply-To: <201504282048.WK91FDRR%fengguang.wu-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
[ +cc Rob H, Grant L, devicetree ]
On 04/28/2015 08:24 AM, kbuild test robot wrote:
> tree: git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/tty.git tty-testing
> head: 962a6a5ce6b8280d6ce7416ce57a36103d31a523
> commit: 5a95cfdfaf5cb960ea06f333323dbe85ed269abf [9/30] of: earlycon: Fix 'stdout-path' with ':' path terminator
> config: microblaze-mmu_defconfig (attached as .config)
> reproduce:
> wget https://git.kernel.org/cgit/linux/kernel/git/wfg/lkp-tests.git/plain/sbin/make.cross -O ~/bin/make.cross
> chmod +x ~/bin/make.cross
> git checkout 5a95cfdfaf5cb960ea06f333323dbe85ed269abf
> # save the attached .config to linux build tree
> make.cross ARCH=microblaze
>
> All error/warnings:
>
> drivers/of/fdt.c: In function 'early_init_dt_scan_chosen_serial':
>>> drivers/of/fdt.c:807:2: error: implicit declaration of function 'fdt_path_offset_namelen' [-Werror=implicit-function-declaration]
> offset = fdt_path_offset_namelen(fdt, p, (int)(q - p));
> ^
> cc1: some warnings being treated as errors
Greg,
This error occurs because the patch "libfdt: Add fdt_path_offset_namelen()"
has not been upstreamed yet by the devicetree maintainers.
Please back out commits 5a95cfdfaf5c ("of: earlycon: Fix 'stdout-path' with ':' path terminator")
through 865f9cc509db ("of: earlycon: Log more helpful message if earlycon not found")
from tty-testing.
I'll just resend the series when the situation with the missing
commit has been sorted.
Regards,
Peter Hurley
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next parent reply other threads:[~2015-04-28 13:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <201504282048.WK91FDRR%fengguang.wu@intel.com>
[not found] ` <201504282048.WK91FDRR%fengguang.wu-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
2015-04-28 13:26 ` Peter Hurley [this message]
[not found] ` <553F8A6D.9040404-WaGBZJeGNqdsbIuE7sb01tBPR1lH4CV8@public.gmane.org>
2015-04-28 21:30 ` [tty:tty-testing 9/30] drivers/of/fdt.c:807:2: error: implicit declaration of function 'fdt_path_offset_namelen' Greg Kroah-Hartman
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=553F8A6D.9040404@hurleysoftware.com \
--to=peter-wagbzjegnqdsbiue7sb01tbpr1lh4cv8@public.gmane.org \
--cc=devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=fengguang.wu-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
--cc=grant.likely-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org \
--cc=gregkh-hQyY1W1yCW8ekmWlsbkhG0B+6BGkLq7r@public.gmane.org \
--cc=kbuild-all-JC7UmRfGjtg@public.gmane.org \
--cc=robh+dt-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.