On Tue, May 12, 2009 at 11:55:57PM +0200, Martin Michlmayr wrote: > * Thomas Bogendoerfer <tsbogend@xxxxxxxxxxxxxxxx> [2009-05-04 23:51]: > > Locking of irq_desc is now done in irq_set_affinity; Don't lock it > > again in chip specific set_affinity function. > > SWARM boots with this patch, but dmesg shows: > > [17179570.260000] attempted to set irq affinity for irq 8 to multiple CPUs > [17179570.484000] attempted to set irq affinity for irq 8 to multiple CPUs > [17179570.500000] attempted to set irq affinity for irq 8 to multiple CPUs I saw them as well, either the caller of set_irq_affinity does something illegal or the API has changed and the message just should go away... Thomas. -- Crap can work. Given enough thrust pigs will fly, but it's not necessary a good idea. [ RFC1925, 2.3 ]
