From: buytenh@wantstofly.org (Lennert Buytenhek)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: mxs: irq_data conversion
Date: Sat, 22 Jan 2011 02:16:39 +0100 [thread overview]
Message-ID: <20110122011639.GA27938@mail.wantstofly.org> (raw)
In-Reply-To: <20110121104742.GC23596@mail.wantstofly.org>
On Fri, Jan 21, 2011 at 11:47:42AM +0100, Lennert Buytenhek wrote:
> > so... patches welcome.
>
> I'll submit a patch for the above, and to make sure I'll build all
> defconfigs on current -devel as well.
Results:
ag5evm_defconfig fails with:
arch/arm/mach-shmobile/built-in.o: In function `ag5evm_init':
board-ag5evm.c:(.init.text+0x238): undefined reference to `sh73a0_pinmux_init'
which isn't my fault.
iop32x_defconfig fails with:
/tmp/ccLtyaJK.s: Assembler messages:
/tmp/ccLtyaJK.s:1468: Error: selected processor does not support `movt r2,32768'
make[3]: *** [drivers/net/r8169.o] Error 1
which isn't immediately obvious (but also doesn't seem to be my fault).
magician_defconfig fails with:
/data/buytenh/kern.irqdata/linux-2.6/drivers/mfd/asic3.c: In function ?asic3_irq_demux?:
/data/buytenh/kern.irqdata/linux-2.6/drivers/mfd/asic3.c:146:6: error: ?struct irq_desc? has no member named ?chip?
/data/buytenh/kern.irqdata/linux-2.6/drivers/mfd/asic3.c:148:13: error: ?struct irq_desc? has no member named ?handler_data?
make[3]: *** [drivers/mfd/asic3.o] Error 1
for which I've submitted a patch here (my original mfd asic3 irq_data
patch did address this, but the patch that got merged instead didn't):
http://marc.info/?l=linux-kernel&m=129565853125126&w=2
mx3_defconfig fails with:
/data/buytenh/kern.irqdata/linux-2.6/drivers/dma/ipu/ipu_irq.c:349:2: error: unknown field ?ack? specified in initializer
/data/buytenh/kern.irqdata/linux-2.6/drivers/dma/ipu/ipu_irq.c:349:2: warning: initialization from incompatible pointer type
/data/buytenh/kern.irqdata/linux-2.6/drivers/dma/ipu/ipu_irq.c:350:2: error: unknown field ?mask? specified in initializer
/data/buytenh/kern.irqdata/linux-2.6/drivers/dma/ipu/ipu_irq.c:350:2: warning: initialization from incompatible pointer type
/data/buytenh/kern.irqdata/linux-2.6/drivers/dma/ipu/ipu_irq.c:351:2: error: unknown field ?unmask? specified in initializer
/data/buytenh/kern.irqdata/linux-2.6/drivers/dma/ipu/ipu_irq.c:351:2: warning: initialization from incompatible pointer type
make[4]: *** [drivers/dma/ipu/ipu_irq.o] Error 1
for which I've (re)submitted a patch here:
http://marc.info/?l=linux-kernel&m=129565867725213&w=2
u8500_defconfig fails with:
arch/arm/mach-ux500/built-in.o:(.data+0x2c04): undefined reference to `ab8500_regulators'
make[1]: *** [.tmp_vmlinux1] Error 1
which isn't my fault.
The rest of the defconfigs build fine. So I think that turning on
GENERIC_HARDIRQS_NO_DEPRECATED for ARM should be OK.
next prev parent reply other threads:[~2011-01-22 1:16 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-21 9:01 [PATCH] ARM: mxs: irq_data conversion Uwe Kleine-König
2011-01-21 9:43 ` Russell King - ARM Linux
2011-01-21 10:15 ` Uwe Kleine-König
2011-01-21 10:27 ` Russell King - ARM Linux
2011-01-21 10:47 ` Lennert Buytenhek
2011-01-21 10:52 ` Russell King - ARM Linux
2011-01-22 1:16 ` Lennert Buytenhek [this message]
2011-01-21 10:28 ` Lennert Buytenhek
2011-01-21 10:45 ` Russell King - ARM Linux
2011-01-21 20:07 ` [PATCH v2] " Uwe Kleine-König
2011-01-22 0:23 ` Lennert Buytenhek
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=20110122011639.GA27938@mail.wantstofly.org \
--to=buytenh@wantstofly.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).