From: Ralf Baechle <ralf@linux-mips.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: LKML <linux-kernel@vger.kernel.org>,
davem@davemloft.net, tony.luck@intel.com, schwidefsky@de.ibm.com
Subject: Re: [PATCH] Consolidate the last compat sigvals
Date: Wed, 16 Feb 2005 17:44:06 +0000 [thread overview]
Message-ID: <20050216174406.GA12946@linux-mips.org> (raw)
In-Reply-To: <20050215154648.74e54fff.sfr@canb.auug.org.au>
On Tue, Feb 15, 2005 at 03:46:48PM +1100, Stephen Rothwell wrote:
> This patch just consolidates the last of the (what should have been)
> compat_sigval_ts. It worries me that S390 has a sigval_t in its struct
> compat_siginfo, but I have left that for now.
>
> Signed-off-by: Stephen Rothwell <sfr@canb.auug.org.au>
>
> P.S. this patch has not even been compiled as I don't have acces to any of
> the platforms involved, but should be straight forward to fix if it breaks
> anything.
You missed one instance for MIPS. Below patch makes MIPS build.
Ralf
Signed-off-by: Ralf Baechle <ralf@linux-mips.org>
signal32.c | 2 +-
1 files changed, 1 insertion(+), 1 deletion(-)
Index: linux-oprof/arch/mips/kernel/signal32.c
===================================================================
--- linux-oprof.orig/arch/mips/kernel/signal32.c 2005-02-16 17:42:42.000000000 +0000
+++ linux-oprof/arch/mips/kernel/signal32.c 2005-02-16 17:43:46.000000000 +0000
@@ -78,7 +78,7 @@
struct {
timer_t _tid; /* timer id */
int _overrun; /* overrun count */
- sigval_t32 _sigval; /* same as below */
+ compat_sigval_t _sigval;/* same as below */
int _sys_private; /* not to be passed to user */
} _timer;
next prev parent reply other threads:[~2005-02-16 17:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-15 4:46 [PATCH] Consolidate the last compat sigvals Stephen Rothwell
2005-02-15 18:38 ` David S. Miller
2005-02-16 17:44 ` Ralf Baechle [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-03-07 7:00 Stephen Rothwell
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=20050216174406.GA12946@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=schwidefsky@de.ibm.com \
--cc=sfr@canb.auug.org.au \
--cc=tony.luck@intel.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 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.