From: Andrew Morton <akpm@digeo.com>
To: Zwane Mwaikambo <zwane@linuxpower.ca>
Cc: rmk@arm.linux.org.uk, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] protect 'action' in show_interrupts
Date: Fri, 7 Mar 2003 14:01:03 -0800 [thread overview]
Message-ID: <20030307140103.00221e7e.akpm@digeo.com> (raw)
In-Reply-To: <Pine.LNX.4.50.0303071124440.18716-100000@montezuma.mastecende.com>
Zwane Mwaikambo <zwane@linuxpower.ca> wrote:
>
> On Fri, 7 Mar 2003, Russell King wrote:
>
> > We don't have a per-irq_desc spinlock on ARM - it's a global
> > irq_controller_lock.
> >
> > Thanks.
>
> Ok thanks for spotting that. Andrew here it is rediffed.
Thanks, Zwane. Looks good.
I made some adjustments down in mips land - they weren't initialising the
irq_desc_t locks on startup.
That's pretty academic, but doing spin_lock_irqsave() is as good a way as any
of saying "preempt_disable()", and it keeps all the code looking the same.
next prev parent reply other threads:[~2003-03-07 21:55 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-07 5:13 Oops: 2.5.64 check_obj_poison for 'size-64' Zwane Mwaikambo
2003-03-07 6:23 ` Andrew Morton
2003-03-07 7:22 ` Zwane Mwaikambo
2003-03-07 7:35 ` Andrew Morton
2003-03-07 7:40 ` Zwane Mwaikambo
2003-03-07 7:45 ` Miles Bader
2003-03-07 7:58 ` Andrew Morton
2003-03-07 8:10 ` Miles Bader
2003-03-07 10:05 ` [PATCH] protect 'action' in show_interrupts Zwane Mwaikambo
2003-03-07 10:28 ` Andrew Morton
2003-03-07 15:32 ` Zwane Mwaikambo
2003-03-07 15:46 ` Russell King
2003-03-07 16:25 ` Zwane Mwaikambo
2003-03-07 22:01 ` Andrew Morton [this message]
[not found] ` <Pine.LNX.4.50.0303070351060.18716-100000@montezuma.mastecende.com>
[not found] ` <20030307010539.3c0a14a3.akpm@digeo.com>
2003-03-07 9:53 ` Oops: 2.5.64 check_obj_poison for 'size-64' Zwane Mwaikambo
2003-03-07 19:38 ` Manfred Spraul
2003-03-07 21:57 ` Zwane Mwaikambo
2003-03-08 2:11 ` Zwane Mwaikambo
2003-03-08 2:24 ` Andrew Morton
2003-03-08 2:42 ` Zwane Mwaikambo
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=20030307140103.00221e7e.akpm@digeo.com \
--to=akpm@digeo.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rmk@arm.linux.org.uk \
--cc=zwane@linuxpower.ca \
/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