All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg Ungerer <gerg@snapgear.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: linux-m68k@vger.kernel.org, uclinux-dev@uclinux.org,
	Greg Ungerer <gerg@uclinux.org>
Subject: Re: [PATCH] m68k: make fp register stores consistent for m68k and ColdFire
Date: Fri, 4 Nov 2011 11:14:50 +1000	[thread overview]
Message-ID: <4EB33C8A.5020000@snapgear.com> (raw)
In-Reply-To: <CAMuHMdVdwKG7jyTTi7Xbx11Avj=kLQL7wVV0gXwuZ71FQG5KPg@mail.gmail.com>

Hi Geert,

On 03/11/11 18:23, Geert Uytterhoeven wrote:
> On Thu, Nov 3, 2011 at 06:58,<gerg@snapgear.com>  wrote:
>> From: Greg Ungerer<gerg@uclinux.org>
>>
>> There is no reason we can't make the saved fp registers the same for all
>> m68k types and ColdFire. There is a little wasted space, but the code
>> consistentcy and cleanliness is a big win.
>
> consistency

I really need to spell check these :-)


>> sigcontext.h is an exported header, but currently there is no in-mainline
>> users of the !__uClinux__ and __mcoldfire__ case that this change effects.
>> Even better this change actually makes this structure consistent with
>> the out-of-mainline ColdFire/MMU code.
>>
>> Signed-off-by: Greg Ungerer<gerg@uclinux.org>
>
> Acked-by: Geert Uytterhoeven<geert@linux-m68k.org>

Thanks!

Regards
Greg


------------------------------------------------------------------------
Greg Ungerer  --  Principal Engineer        EMAIL:     gerg@snapgear.com
SnapGear Group, McAfee                      PHONE:       +61 7 3435 2888
8 Gardner Close                             FAX:         +61 7 3217 5323
Milton, QLD, 4064, Australia                WEB: http://www.SnapGear.com

      reply	other threads:[~2011-11-04  1:13 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-03  5:58 [PATCH] m68k: make fp register stores consistent for m68k and ColdFire gerg
2011-11-03  8:23 ` Geert Uytterhoeven
2011-11-04  1:14   ` Greg Ungerer [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=4EB33C8A.5020000@snapgear.com \
    --to=gerg@snapgear.com \
    --cc=geert@linux-m68k.org \
    --cc=gerg@uclinux.org \
    --cc=linux-m68k@vger.kernel.org \
    --cc=uclinux-dev@uclinux.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.