Ultralinux archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Alexandr Kanevskiy <kad@crystalowl.net>
To: ultralinux@vger.kernel.org
Subject: small patch to fix compilation 2.4.31/sparc64
Date: Sun, 16 Oct 2005 19:21:31 +0000	[thread overview]
Message-ID: <1129490491.21366.9.camel@orava.homeip.net> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 215 bytes --]

Hi.

I tried to build 2.4.31 on sparc64, and found minor problem. 
Patch for it attached, and I hope it will be useful for maintainers
before next 2.4.x release.

-- 
Alexandr Kanevskiy <kad@crystalowl.net>

[-- Attachment #1.2: linux-2.4.31-__bzero_noasi-fix.patch --]
[-- Type: text/x-patch, Size: 760 bytes --]

diff -ru linux-2.4.31.org/arch/sparc64/kernel/sparc64_ksyms.c linux-2.4.31/arch/sparc64/kernel/sparc64_ksyms.c
--- linux-2.4.31.org/arch/sparc64/kernel/sparc64_ksyms.c	2005-04-04 04:42:19.000000000 +0300
+++ linux-2.4.31/arch/sparc64/kernel/sparc64_ksyms.c	2005-10-16 21:09:09.000000000 +0300
@@ -63,7 +63,7 @@
 extern void die_if_kernel(char *str, struct pt_regs *regs);
 void _sigpause_common (unsigned int set, struct pt_regs *);
 extern void *__bzero(void *, size_t);
-extern void *__bzero_noasi(void *, size_t);
+extern __kernel_size_t __bzero_noasi(void *, __kernel_size_t);
 extern void *__memscan_zero(void *, size_t);
 extern void *__memscan_generic(void *, int, size_t);
 extern int __memcmp(const void *, const void *, __kernel_size_t);

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

                 reply	other threads:[~2005-10-16 19:21 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=1129490491.21366.9.camel@orava.homeip.net \
    --to=kad@crystalowl.net \
    --cc=ultralinux@vger.kernel.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).