mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Colin Leroy" <colin@colino.net>
To: "Tom Rini" <trini@kernel.crashing.org>
Cc: <benh@kernel.crashing.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] 2.6.4-bk3 ppc32 compile fix
Date: Mon, 15 Mar 2004 17:03:16 +0100	[thread overview]
Message-ID: <036801c40aa7$06d40170$3cc8a8c0@epro.dom> (raw)
In-Reply-To: <20040315160313.GB4342@smtp.west.cox.net>

[-- Attachment #1: Type: text/plain, Size: 250 bytes --]

Hi again,

> The problem is that on PPC32 (and probably sparc64) 'asmlinkage' is a
> useless keyword, and should just be removed from
> include/asm-ppc/unistd.h.

Here's another patch, then :)
(not changing sparc64 stuff... I can't test it)
-- 
Colin

[-- Attachment #2: asmlinkage.diff --]
[-- Type: application/octet-stream, Size: 620 bytes --]

--- include/asm-ppc/unistd.h.orig	2004-03-11 03:55:23.000000000 +0100
+++ include/asm-ppc/unistd.h	2004-03-15 17:01:49.000000000 +0100
@@ -415,10 +415,10 @@
 int sys_pipe(int __user *fildes);
 int sys_ptrace(long request, long pid, long addr, long data);
 struct sigaction;
-asmlinkage long sys_rt_sigaction(int sig,
-				const struct sigaction __user *act,
-				struct sigaction __user *oact,
-				size_t sigsetsize);
+long sys_rt_sigaction(int sig,
+		      const struct sigaction __user *act,
+		      struct sigaction __user *oact,
+		      size_t sigsetsize);
 
 #endif /* __KERNEL_SYSCALLS__ */
 

  reply	other threads:[~2004-03-15 16:08 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-14 21:59 Colin Leroy
2004-03-15 15:51 ` Tom Rini
2004-03-15 15:49   ` Colin Leroy
2004-03-15 16:03     ` Tom Rini
2004-03-15 16:03       ` Colin Leroy [this message]
2004-03-15 16:12         ` Tom Rini

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='036801c40aa7$06d40170$3cc8a8c0@epro.dom' \
    --to=colin@colino.net \
    --cc=benh@kernel.crashing.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=trini@kernel.crashing.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

all inboxes | Powered by JetHome®