From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Linus Torvalds <torvalds@osdl.org>, Andrew Morton <akpm@osdl.org>
Cc: linux-m68k@vger.kernel.org,
Linux Kernel list <linux-kernel@vger.kernel.org>
Subject: m68knommu doesn't build upstream
Date: Fri, 17 Nov 2006 15:51:44 +1100 [thread overview]
Message-ID: <1163739105.5940.431.camel@localhost.localdomain> (raw)
While looking into getting rid of the old compat dma-mapping stuff,
which is only used by a handful of archs, I've built some cross
toolchains for those archs in order to at least test build my changes.
It looks however that one of them, m68knommu, doesn't build with
upstream git and a defconfig
In file included from arch/m68knommu/kernel/asm-offsets.c:18:
include/asm/irqnode.h:26: error: conflicting types for 'irq_handler_t'
include/linux/interrupt.h:67: error: previous declaration of 'irq_handler_t' was here
Is this arch bitrotting ?
Cheers,
Ben.
next reply other threads:[~2006-11-17 4:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-17 4:51 Benjamin Herrenschmidt [this message]
2006-11-17 5:17 ` m68knommu doesn't build upstream Geert Uytterhoeven
2006-11-20 5:46 ` Greg Ungerer
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=1163739105.5940.431.camel@localhost.localdomain \
--to=benh@kernel.crashing.org \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-m68k@vger.kernel.org \
--cc=torvalds@osdl.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox