Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
To: Martin Michlmayr <tbm@cyrius.com>
Cc: linux-mips@linux-mips.org, ralf@linux-mips.org
Subject: Re: [PATCH] SIBYTE: fix locking in set_irq_affinity
Date: Thu, 14 May 2009 15:20:30 +0200	[thread overview]
Message-ID: <20090514132030.GA7926@alpha.franken.de> (raw)
In-Reply-To: <20090512215556.GA4774@deprecation.cyrius.com>

On Tue, May 12, 2009 at 11:55:57PM +0200, Martin Michlmayr wrote:
> * Thomas Bogendoerfer <tsbogend@alpha.franken.de> [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 ]

  reply	other threads:[~2009-05-14 13:20 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-04 21:51 [PATCH] SIBYTE: fix locking in set_irq_affinity Thomas Bogendoerfer
2009-05-07 14:53 ` Ralf Baechle
2009-05-12 21:55 ` Martin Michlmayr
2009-05-14 13:20   ` Thomas Bogendoerfer [this message]
2009-05-14 13:48     ` Ralf Baechle

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=20090514132030.GA7926@alpha.franken.de \
    --to=tsbogend@alpha.franken.de \
    --cc=linux-mips@linux-mips.org \
    --cc=ralf@linux-mips.org \
    --cc=tbm@cyrius.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