From: Ralf Baechle <ralf@linux-mips.org>
To: Atsushi Nemoto <anemo@mba.ocn.ne.jp>
Cc: linux-mips@linux-mips.org, mlachwani@mvista.com
Subject: Re: [PATCH] Make sure cpu_has_fpu is used only in atomic context
Date: Mon, 9 Oct 2006 17:02:15 +0100 [thread overview]
Message-ID: <20061009160215.GA7642@linux-mips.org> (raw)
In-Reply-To: <20061009.001001.74753036.anemo@mba.ocn.ne.jp>
On Mon, Oct 09, 2006 at 12:10:01AM +0900, Atsushi Nemoto wrote:
> Make sure cpu_has_fpu (which uses smp_processor_id()) is used
> only in atomic context.
It's awfully ugly to have an increasing number of preemption kludgery
around but it's not so trivial to avoid unfortunately ...
Ralf
prev parent reply other threads:[~2006-10-09 16:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <44F715F2.7050305@mvista.com>
[not found] ` <20060901.122527.63741495.nemoto@toshiba-tops.co.jp>
[not found] ` <20060901.170817.118968734.nemoto@toshiba-tops.co.jp>
2006-10-08 15:10 ` [PATCH] Make sure cpu_has_fpu is used only in atomic context Atsushi Nemoto
2006-10-09 16:02 ` Ralf Baechle [this message]
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=20061009160215.GA7642@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=anemo@mba.ocn.ne.jp \
--cc=linux-mips@linux-mips.org \
--cc=mlachwani@mvista.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