mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Russell King <rmk@arm.linux.org.uk>
To: linux-kernel@vger.kernel.org
Subject: [Patch] 2.4.2: af_unix.c warnings
Date: Thu, 22 Feb 2001 13:53:40 +0000 (GMT)	[thread overview]
Message-ID: <200102221353.f1MDrfq30420@flint.arm.linux.org.uk> (raw)

Hi,

In 2.4.2 with CONFIG_SYSCTL=n, I'm seeing the following warnings
while compiling af_unix.c:

gcc -D__KERNEL__ -I/usr/src/v2.4/linux-p720t/include -Wall -Wstrict-prototypes -O2  -fno-strict-aliasing -fno-common -pipe -mapcs-32 -march=armv4 -mtune=arm7tdmi -mshort-load-bytes -msoft-float    -c -o af_unix.o af_unix.c
af_unix.c:1855: warning: return-type defaults to `int'
af_unix.c:1855: warning: function declaration isn't a prototype
af_unix.c: In function `unix_sysctl_register':
af_unix.c:1855: warning: control reaches end of non-void function
af_unix.c: At top level:
af_unix.c:1856: warning: return-type defaults to `int'
af_unix.c:1856: warning: function declaration isn't a prototype
af_unix.c: In function `unix_sysctl_unregister':
af_unix.c:1856: warning: control reaches end of non-void function

The following patch fixes these warnings:

--- orig/net/unix/af_unix.c	Thu Feb 22 11:25:50 2001
+++ linux/net/unix/af_unix.c	Thu Feb 22 13:54:41 2001
@@ -1852,8 +1852,8 @@
 extern void unix_sysctl_register(void);
 extern void unix_sysctl_unregister(void);
 #else
-static inline unix_sysctl_register() {};
-static inline unix_sysctl_unregister() {};
+static inline void unix_sysctl_register(void) {}
+static inline void unix_sysctl_unregister(void) {}
 #endif
 
 static const char banner[] __initdata = KERN_INFO "NET4: Unix domain sockets 1.0/SMP for Linux NET4.0.\n";
 

--
Russell King (rmk@arm.linux.org.uk)                The developer of ARM Linux
             http://www.arm.linux.org.uk/personal/aboutme.html


             reply	other threads:[~2001-02-22 14:32 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-02-22 13:53 Russell King [this message]
2001-02-23  1:34 ` David S. Miller

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=200102221353.f1MDrfq30420@flint.arm.linux.org.uk \
    --to=rmk@arm.linux.org.uk \
    --cc=linux-kernel@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

all inboxes | Powered by JetHome®