aboutsummaryrefslogtreecommitdiffstats
path: root/drivers/net/bonding
diff options
context:
space:
mode:
authorDeepak Saxena <dsaxena@plexity.net>2006-12-04 18:04:46 -0500
committerJeff Garzik <jeff@garzik.org>2006-12-04 18:36:02 -0500
commit33fee56ae846cdee67d2ab6d14c3baa879dfc794 (patch)
tree96995a7c5971069168cbcd9bd18f5269dc72737d /drivers/net/bonding
parent2ad657c88d8b3c1f97c1b8cc474b6307ba7f8509 (diff)
[PATCH] Update smc91x driver with ARM Versatile board info
We need to specify a Versatile-specific SMC_IRQ_FLAGS value or the new generic IRQ layer will complain thusly: No IRQF_TRIGGER set_type function for IRQ 25 (<NULL>) Signed-off-by: Deepak Saxena <dsaxena@plexity.net> Cc: Jeff Garzik <jeff@garzik.org> Cc: Russell King <rmk@arm.linux.org.uk> Cc: Nicolas Pitre <nico@cam.org> On Fri, 20 Oct 2006 22:50:40 +0100 Russell King <rmk@arm.linux.org.uk> wrote: > On Fri, Oct 20, 2006 at 02:42:04PM -0700, akpm@osdl.org wrote: > > We need to specify a Versatile-specific SMC_IRQ_FLAGS value or the new > > generic IRQ layer will complain thusly: > > I don't think I heard anything back from my previous suggestion that > the IRQ flags are passed through the platform device IRQ resource. > > Doing so would avoid adding yet another platform specific block into > the file. > > BTW, Integrator platforms will also suffer from this, which will add > another ifdef to this header. > > Let's do it right and arrange to pass these flags from the platform > code. It's not like they're in a critical path. Signed-off-by: Andrew Morton <akpm@osdl.org> Signed-off-by: Jeff Garzik <jeff@garzik.org>
Diffstat (limited to 'drivers/net/bonding')
0 files changed, 0 insertions, 0 deletions