From: robherring2@gmail.com (Rob Herring)
To: linux-arm-kernel@lists.infradead.org
Subject: linux-next arm64 randconfig errors
Date: Fri, 19 Apr 2013 17:42:37 -0500 [thread overview]
Message-ID: <5171C85D.8020909@gmail.com> (raw)
Here are errors in today's linux-next for arm64. Looks like most are missing arch pieces.
of_get_next_parent has a fix pending.
Rob
arch/arm64/kernel/early_printk.c:98:23: error: conflicting types for 'early_console'
drivers/base/regmap/regmap-mmio.c:120:4: error: implicit declaration of function 'readq' [-Werror=implicit-function-declaration]
drivers/base/regmap/regmap-mmio.c:64:4: error: implicit declaration of function 'writeq' [-Werror=implicit-function-declaration]
drivers/block/blockconsole.c:164:2: error: implicit declaration of function 'cmpxchg64' [-Werror=implicit-function-declaration]
drivers/dma/amba-pl08x.c:303:13: error: expected identifier before '(' token
drivers/gpio/gpio-generic.c:103:2: error: implicit declaration of function 'readq' [-Werror=implicit-function-declaration]
drivers/gpio/gpio-generic.c:98:2: error: implicit declaration of function 'writeq' [-Werror=implicit-function-declaration]
drivers/mfd/tps65912-core.c:147: undefined reference to `mfd_add_devices'
drivers/mfd/tps65912-core.c:164: undefined reference to `mfd_remove_devices'
drivers/mfd/tps65912-core.c:171: undefined reference to `mfd_remove_devices'
drivers/parport/parport_pc.c:67:25: fatal error: asm/parport.h: No such file or directory
ERROR: "of_get_next_parent" [drivers/media/v4l2-core/videodev.ko] undefined!
ERROR: "read_current_timer" [crypto/tcrypt.ko] undefined!
include/linux/vt_buffer.h:18:21: fatal error: asm/vga.h: No such file or directory
include/video/vga.h:22:21: fatal error: asm/vga.h: No such file or directory
reply other threads:[~2013-04-19 22:42 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=5171C85D.8020909@gmail.com \
--to=robherring2@gmail.com \
--cc=linux-arm-kernel@lists.infradead.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.