From: Ralf Baechle <ralf@linux-mips.org>
To: Atsushi Nemoto <anemo@mba.ocn.ne.jp>
Cc: linux-mips@linux-mips.org
Subject: Re: [PATCH] unify mips_fpu_soft_struct and mips_fpu_hard_struct
Date: Mon, 15 May 2006 18:06:11 +0100 [thread overview]
Message-ID: <20060515170611.GA30806@linux-mips.org> (raw)
In-Reply-To: <20060516.012603.41010976.anemo@mba.ocn.ne.jp>
On Tue, May 16, 2006 at 01:26:03AM +0900, Atsushi Nemoto wrote:
> The struct mips_fpu_soft_struct and mips_fpu_hard_struct are
> completely same now and the kernel fpu emulator assumes that. This
> patch unifies them to mips_fpu_struct and get rid of mips_fpu_union.
>
> Signed-off-by: Atsushi Nemoto <anemo@mba.ocn.ne.jp>
Indeed, one of the things I always meant to do. The split into an
emulator and a hardware structure goes back to day one of the kernel when
I copied that from i386.
Queued,
Ralf
next prev parent reply other threads:[~2006-05-15 17:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-15 16:26 [PATCH] unify mips_fpu_soft_struct and mips_fpu_hard_struct Atsushi Nemoto
2006-05-15 17:06 ` Ralf Baechle [this message]
2006-05-16 10:44 ` 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=20060515170611.GA30806@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=anemo@mba.ocn.ne.jp \
--cc=linux-mips@linux-mips.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