public inbox for linux-next@vger.kernel.org 
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb•auug.org.au>
To: "David S. Miller" <davem@davemloft•net>
Cc: linux-next@vger•kernel.org, linux-kernel@vger•kernel.org,
	Kristoffer Glembo <kristoffer@gaisler•com>
Subject: linux-next: sparc tree build failure
Date: Thu, 5 Nov 2009 18:50:14 +1100	[thread overview]
Message-ID: <20091105185014.76dd0d31.sfr@canb.auug.org.au> (raw)

Hi Dave,

Today's linux-next build (powerpc allyesconfig) failed like this:

drivers/serial/apbuart.c:32:23: error: asm/oplib.h: No such file or directory
drivers/serial/apbuart.c:586: error: variable 'grlib_apbuart_of_driver' has initializer but incomplete type
drivers/serial/apbuart.c:587: error: unknown field 'match_table' specified in initializer
drivers/serial/apbuart.c:587: warning: excess elements in struct initializer
drivers/serial/apbuart.c:587: warning: (near initialization for 'grlib_apbuart_of_driver')
drivers/serial/apbuart.c:588: error: unknown field 'probe' specified in initializer
drivers/serial/apbuart.c:588: warning: excess elements in struct initializer
drivers/serial/apbuart.c:588: warning: (near initialization for 'grlib_apbuart_of_driver')
drivers/serial/apbuart.c:589: error: unknown field 'driver' specified in initializer
drivers/serial/apbuart.c:589: error: extra brace group at end of initializer
drivers/serial/apbuart.c:589: error: (near initialization for 'grlib_apbuart_of_driver')
drivers/serial/apbuart.c:592: warning: excess elements in struct initializer
drivers/serial/apbuart.c:592: warning: (near initialization for 'grlib_apbuart_of_driver')
drivers/serial/apbuart.c: In function 'grlib_apbuart_configure':
drivers/serial/apbuart.c:613: error: implicit declaration of function 'prom_getchild'
drivers/serial/apbuart.c:613: error: 'prom_root_node' undeclared (first use in this function)
drivers/serial/apbuart.c:613: error: (Each undeclared identifier is reported only once
drivers/serial/apbuart.c:613: error: for each function it appears in.)
drivers/serial/apbuart.c:614: error: implicit declaration of function 'prom_getint'
drivers/serial/apbuart.c: In function 'grlib_apbuart_init':
drivers/serial/apbuart.c:679: error: implicit declaration of function 'of_register_driver'
drivers/serial/apbuart.c:679: error: 'of_platform_bus_type' undeclared (first use in this function)

Caused by commit d4ac42a582e46d7f86f0acb4253a310423c72c4c ("sparc:
Support for GRLIB APBUART serial port").  I added the following patch for
today.

From: Stephen Rothwell <sfr@canb•auug.org.au>
Date: Thu, 5 Nov 2009 18:40:55 +1100
Subject: [PATCH] sparc: the GRLIB APBUART serial port will only build on sparc

Signed-off-by: Stephen Rothwell <sfr@canb•auug.org.au>
---
 drivers/serial/Kconfig |    1 +
 1 files changed, 1 insertions(+), 0 deletions(-)

diff --git a/drivers/serial/Kconfig b/drivers/serial/Kconfig
index 50943ff..7ec806d 100644
--- a/drivers/serial/Kconfig
+++ b/drivers/serial/Kconfig
@@ -1480,6 +1480,7 @@ config SERIAL_BCM63XX_CONSOLE
 config SERIAL_GRLIB_GAISLER_APBUART
 	tristate "GRLIB APBUART serial support"
 	depends on OF
+	depends on SPARC
 	---help---
 	Add support for the GRLIB APBUART serial port.
 
-- 
1.6.5.2


-- 
Cheers,
Stephen Rothwell                    sfr@canb•auug.org.au
http://www.canb.auug.org.au/~sfr/

             reply	other threads:[~2009-11-05  7:50 UTC|newest]

Thread overview: 48+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-05  7:50 Stephen Rothwell [this message]
2009-11-05  7:53 ` linux-next: sparc tree build failure David Miller
2009-11-05  8:00   ` David Miller
2009-11-05 14:44     ` Kristoffer Glembo
2009-11-13 10:34     ` Kristoffer Glembo
2009-11-13 14:57       ` David Miller
2009-11-13 15:15         ` [PATCH] Use of_find_node_by_path to find root node Kristoffer Glembo
2009-11-13 21:25           ` David Miller
  -- strict thread matches above, loose matches on Subject: below --
2009-11-26  9:16 linux-next: sparc tree build failure Stephen Rothwell
2009-11-26 23:28 ` David Miller
2009-11-27  9:00   ` Thomas Gleixner
2009-11-06  7:02 Stephen Rothwell
2009-11-06  8:19 ` David Miller
2009-11-06  8:26   ` David Miller
2009-11-06  8:27     ` David Miller
2009-11-07  2:35     ` Stephen Rothwell
2009-10-05  7:43 Stephen Rothwell
2009-10-05  7:45 ` David Miller
2009-04-09  5:17 Stephen Rothwell
2009-04-09  5:27 ` Ingo Molnar
2009-04-09  5:28   ` David Miller
2009-04-09  5:36     ` Ingo Molnar
2009-04-09  5:40       ` David Miller
2009-04-09  5:53         ` Ingo Molnar
2009-04-09  5:59           ` David Miller
2009-04-09  5:28 ` David Miller
2009-04-14  3:45 ` Stephen Rothwell
2008-12-04  8:54 Stephen Rothwell
2008-12-04 11:47 ` Sam Ravnborg
2008-12-02  6:24 Stephen Rothwell
2008-12-02 11:22 ` Rusty Russell
2008-12-04  0:04   ` David Miller
2008-11-30 23:46 Stephen Rothwell
2008-12-01  5:41 ` Sam Ravnborg
2008-12-01  7:23   ` David Miller
2008-07-28  6:38 Stephen Rothwell
2008-07-28  8:21 ` Sam Ravnborg
2008-07-28  9:31   ` Adrian Bunk
2008-07-28 15:12     ` Stephen Rothwell
2008-07-28 10:12   ` Stephen Rothwell
2008-07-28 11:16     ` Sam Ravnborg
2008-07-25  7:05 Stephen Rothwell
2008-07-25  7:09 ` Stephen Rothwell
2008-07-26  9:25 ` David Miller
2008-08-04  4:26 ` David Miller
2008-08-04  5:35   ` Stephen Rothwell
2008-07-22  7:41 Stephen Rothwell
2008-07-22 22:47 ` David Miller

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=20091105185014.76dd0d31.sfr@canb.auug.org.au \
    --to=sfr@canb$(echo .)auug.org.au \
    --cc=davem@davemloft$(echo .)net \
    --cc=kristoffer@gaisler$(echo .)com \
    --cc=linux-kernel@vger$(echo .)kernel.org \
    --cc=linux-next@vger$(echo .)kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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