From: Jim Nelson <james4765@cwazy.co.uk>
To: Brian Gerst <bgerst@didntduck.org>
Cc: linux-kernel@vger.kernel.org, linuxppc-dev@ozlabs.org, paulus@samba.org
Subject: Re: [PATCH 0/7] ppc: remove cli()/sti() from arch/ppc/*
Date: Tue, 04 Jan 2005 21:44:06 -0500 [thread overview]
Message-ID: <41DB5476.9040103@cwazy.co.uk> (raw)
In-Reply-To: <41DB4E99.3060200@didntduck.org>
Brian Gerst wrote:
> James Nelson wrote:
>
>> This series of patches is to remove the last cli()/sti() function
>> calls in arch/ppc.
>>
>> These are the only instances in active code that grep could find.
>
>
> Are you sure none of these need real spinlocks instead of just
> disabling interrupts?
>
> --
> Brian Gerst
>
These are for single-processor systems, mostly evaluation boards and
embedded processors. I coudn't find any reference to multiprocessor
setups for the processors in question after a peruse of the code or a
quick google on the boards in question.
Jim
next prev parent reply other threads:[~2005-01-05 2:43 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-04 21:40 [PATCH 0/7] ppc: remove cli()/sti() from arch/ppc/* James Nelson
2005-01-04 21:40 ` [PATCH 1/7] ppc: remove cli()/sti() in arch/ppc/4xx_io/serial_sicc.c James Nelson
2005-01-04 21:40 ` [PATCH 2/7] ppc: remove cli()/sti() in arch/ppc/8xx_io/cs4218_tdm.c James Nelson
2005-01-04 21:40 ` [PATCH 3/7] ppc: remove cli()/sti() in arch/ppc/8xx_io/fec.c James Nelson
2005-01-04 21:40 ` [PATCH 4/7] ppc: remove cli()/sti() in arch/ppc/platforms/apus_setup.c James Nelson
2005-01-04 21:41 ` [PATCH 5/7] ppc: remove cli()/sti() in arch/ppc/platforms/pal4_setup.c James Nelson
2005-01-04 21:41 ` [PATCH 6/7] ppc: remove cli()/sti() in arch/ppc/syslib/m8xx_setup.c James Nelson
2005-01-04 21:41 ` [PATCH 7/7] ppc: remove cli()/sti() in arch/ppc/syslib/qspan_pci.c James Nelson
2005-01-05 2:19 ` [PATCH 0/7] ppc: remove cli()/sti() from arch/ppc/* Brian Gerst
2005-01-05 2:44 ` Jim Nelson [this message]
2005-01-05 9:26 ` Christoph Hellwig
2005-01-05 11:19 ` Jim Nelson
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=41DB5476.9040103@cwazy.co.uk \
--to=james4765@cwazy.co.uk \
--cc=bgerst@didntduck.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=paulus@samba.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