Linux-Next discussions
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: linux-next@vger.kernel.org, Yinghai Lu <yhlu.kernel@gmail.com>,
	Ingo Molnar <mingo@elte.hu>
Subject: linux-next: m68k build failure
Date: Thu, 28 Aug 2008 16:50:04 +1000	[thread overview]
Message-ID: <20080828165004.4d833de6.sfr@canb.auug.org.au> (raw)

[-- Attachment #1: Type: text/plain, Size: 521 bytes --]

Hi Geert,

The m68k allmodconfig build of linux-next (next-20080827) failed like
this:

ERROR: "nr_irqs" [drivers/serial/serial_core.ko] undefined!
ERROR: "nr_irqs" [drivers/serial/8250.ko] undefined!
ERROR: "nr_irqs" [drivers/net/hamradio/baycom_ser_fdx.ko] undefined!

Introduced by the sparseirq tree.

nr_irqs is not exported for m68k.  I will add a patch to add the export to
linux-next today.

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

[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]

             reply	other threads:[~2008-08-28  6:50 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-28  6:50 Stephen Rothwell [this message]
2008-08-28  6:59 ` linux-next: m68k build failure Ingo Molnar
  -- strict thread matches above, loose matches on Subject: below --
2008-12-09  6:45 Stephen Rothwell
2008-12-09  8:00 ` David Miller
2008-12-09  8:50   ` Stephen Rothwell
2008-07-30  7:52 Stephen Rothwell
2008-07-30  7:54 ` Stephen Rothwell
2008-07-30  8:02 ` David Miller
2008-07-30  8:49   ` Sam Ravnborg
2008-08-01  5:37     ` Stephen Rothwell
2008-08-01 13:52       ` Geert Uytterhoeven
2008-08-01 20:41         ` Sam Ravnborg
2008-08-02  4:06           ` Stephen Rothwell
2008-08-03 20:00             ` Geert Uytterhoeven

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=20080828165004.4d833de6.sfr@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=geert@linux-m68k.org \
    --cc=linux-next@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=yhlu.kernel@gmail.com \
    /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