From: Maxim Kuvyrkov <maxim@codesourcery.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Linux/m68k <linux-m68k@lists.linux-m68k.org>
Subject: Re: [git pull] m68k updates for 2.6.34
Date: Wed, 03 Mar 2010 17:08:42 +0300 [thread overview]
Message-ID: <4B8E6D6A.6050108@codesourcery.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1002272207450.9843@ayla.of.borg>
[-- Attachment #1: Type: text/plain, Size: 716 bytes --]
<CC trimmed>
On 2/28/10 12:13 AM, Geert Uytterhoeven wrote:
> Hi Linus,
>
> Please pull to receive the m68k updates for 2.6.34.
>
> The parts that impact m68knommu have been acked by Greg.
> The pmac_zilog parts have been acked by BenH.
>
> Thanks!
...
> m68k: Define sigcontext ABI of ColdFire
I only now have noticed that an old version of this patch was merged in.
The latest version was posted here
(http://marc.info/?l=linux-m68k&m=126571455916199&w=2) and included a
fix for the libSegFault to not overflow sc_fpstate field [I got the math
wrong the first time round].
The attached patch fixes this problem.
Thanks,
--
Maxim Kuvyrkov
CodeSourcery
maxim@codesourcery.com
(650) 331-3385 x724
[-- Attachment #2: 0001-Fix-struct-sigcontext-for-ColdFire.patch --]
[-- Type: text/plain, Size: 1162 bytes --]
>From de4c0f12fd2fd3e8436218dfb5edba3b3d570ee0 Mon Sep 17 00:00:00 2001
From: Maxim Kuvyrkov <maxim@codesourcery.com>
Date: Wed, 3 Mar 2010 16:53:45 +0300
Subject: [PATCH] Fix `struct sigcontext' for ColdFire
LibSegFault uses piggybacks sc_fpstate field of the `struct sigcontext'
and this patch avoids LibSegFault overflowing this field. Also this
removes an unnecessary divergence from classic m68k.
Signed-off-by: Maxim Kuvyrkov <maxim@codesourcery.com>
---
arch/m68k/include/asm/sigcontext.h | 4 +---
1 files changed, 1 insertions(+), 3 deletions(-)
diff --git a/arch/m68k/include/asm/sigcontext.h b/arch/m68k/include/asm/sigcontext.h
index 1320eaa..a29dd74 100644
--- a/arch/m68k/include/asm/sigcontext.h
+++ b/arch/m68k/include/asm/sigcontext.h
@@ -17,13 +17,11 @@ struct sigcontext {
#ifndef __uClinux__
# ifdef __mcoldfire__
unsigned long sc_fpregs[2][2]; /* room for two fp registers */
- unsigned long sc_fpcntl[3];
- unsigned char sc_fpstate[16+6*8];
# else
unsigned long sc_fpregs[2*3]; /* room for two fp registers */
+# endif
unsigned long sc_fpcntl[3];
unsigned char sc_fpstate[216];
-# endif
#endif
};
--
1.6.6.1
next prev parent reply other threads:[~2010-03-03 14:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-27 21:13 [git pull] m68k updates for 2.6.34 Geert Uytterhoeven
2010-03-03 14:08 ` Maxim Kuvyrkov [this message]
2010-03-07 9:43 ` Geert Uytterhoeven
-- strict thread matches above, loose matches on Subject: below --
2010-03-29 18:52 Geert Uytterhoeven
[not found] <alpine.DEB.2.00.1003292048530.3832@ayla.of.borg>
2010-04-14 17:56 ` Geert Uytterhoeven
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=4B8E6D6A.6050108@codesourcery.com \
--to=maxim@codesourcery.com \
--cc=geert@linux-m68k.org \
--cc=linux-m68k@lists.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