From: Greg Ungerer <gerg@snapgear.com>
To: Maxim Kuvyrkov <maxim@codesourcery.com>
Cc: Geert Uytterhoeven <geert@linux-m68k.org>,
Andreas Schwab <schwab@linux-m68k.org>,
Linux/m68k <linux-m68k@vger.kernel.org>
Subject: Re: [PATCH] Define sigcontext ABI for ColdFire
Date: Wed, 10 Feb 2010 16:16:55 +1000 [thread overview]
Message-ID: <4B724F57.1070505@snapgear.com> (raw)
In-Reply-To: <4B714579.3060508@codesourcery.com>
Hi Maxim,
Maxim Kuvyrkov wrote:
> On 9/23/09 1:37 AM, Maxim Kuvyrkov wrote:
>> Maxim Kuvyrkov wrote:
>>> The following patch define sigcontext ABI of ColdFire.
> ...
>> I was lured into thinking that the above sequence is OK by m68knommu's
>> version of the trampoline. Arch/m68knommu/kernel/entry.S uses "move
>> #__NR_rt_sigreturn,%d0" which assembles into "move.w". This is too is
>> buggy and I'm also attaching the fix for the nommu version.
>
> I have cleaned up the sigcontext patch for ColdFire to only touch the
> necessary fields in the sigcontext structure. Attached are the cleaned
> up sigcontext patch and the rt_sigreturn fix for m68knommu.
>
> I hope these patches will find their way into m68k/for-2.6.34 branch.
I'll take 0002-Fix-m68k-uclinux-s-rt_sigreturn-trampoline.patch
and apply to the m68knommu git tree.
Thanks
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
prev parent reply other threads:[~2010-02-10 6:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-18 10:28 [PATCH] Define sigcontext ABI of ColdFire Maxim Kuvyrkov
2009-09-22 21:37 ` Maxim Kuvyrkov
2009-11-09 9:42 ` Maxim Kuvyrkov
2010-02-09 11:22 ` [PATCH] Define sigcontext ABI for ColdFire Maxim Kuvyrkov
2010-02-10 6:16 ` 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=4B724F57.1070505@snapgear.com \
--to=gerg@snapgear.com \
--cc=geert@linux-m68k.org \
--cc=linux-m68k@vger.kernel.org \
--cc=maxim@codesourcery.com \
--cc=schwab@linux-m68k.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