From: Rusty Russell <rusty@rustcorp.com.au>
To: Geert Uytterhoeven <Geert.Uytterhoeven@sonycom.com>
Cc: Linux Kernel Development <linux-kernel@vger.kernel.org>,
torvalds@osdl.org
Subject: Re: [PATCH] scripts/modpost warning
Date: Mon, 01 Mar 2004 17:00:51 +1100 [thread overview]
Message-ID: <20040301062725.6AF702C2FB@lists.samba.org> (raw)
In-Reply-To: Your message of "Sun, 29 Feb 2004 17:15:35 BST." <Pine.GSO.4.58.0402291713230.7483@waterleaf.sonytel.be>
In message <Pine.GSO.4.58.0402291713230.7483@waterleaf.sonytel.be> you write:
>
> I need the following patch to kill a warning (__endian() may be unused) when
> cross-compiling m68k kernels on an ia32 box.
Yep. sumversion.c doesn't actually use this routine.
Please apply.
Rusty.
--
Anyone who quotes me in their sig is an idiot. -- Rusty Russell.
From: Geert Uytterhoeven <Geert.Uytterhoeven@sonycom.com>
I need the following patch to kill a warning (__endian() may be unused) when
cross-compiling m68k kernels on an ia32 box.
sumversion.c include modpost.h for grab_file and release_file, and
doesn't use __endian.
--- linux-2.6.4-rc1/scripts/modpost.h 2004-02-29 09:33:41.000000000 +0100
+++ linux-m68k-2.6.4-rc1/scripts/modpost.h 2004-02-29 10:39:56.000000000 +0100
@@ -31,7 +31,7 @@
#if KERNEL_ELFDATA != HOST_ELFDATA
-static void __endian(const void *src, void *dest, unsigned int size)
+static inline void __endian(const void *src, void *dest, unsigned int size)
{
unsigned int i;
for (i = 0; i < size; i++)
next prev parent reply other threads:[~2004-03-01 6:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-29 16:15 Geert Uytterhoeven
2004-03-01 6:00 ` Rusty Russell [this message]
2004-03-01 14:02 ` Kai Germaschewski
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=20040301062725.6AF702C2FB@lists.samba.org \
--to=rusty@rustcorp.com.au \
--cc=Geert.Uytterhoeven@sonycom.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.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®