All of lore.kernel.org
 help / color / mirror / Atom feed
From: Adrian Bunk <bunk@stusta.de>
To: netdev@oss.sgi.com, linux-kernel@vger.kernel.org
Subject: [2.6 patch] net/socket.c: make a function static
Date: Sun, 12 Dec 2004 22:15:06 +0100	[thread overview]
Message-ID: <20041212211506.GY22324@stusta.de> (raw)

The patch below makes a needlessly global function static.


diffstat output:
 include/linux/net.h |    4 ----
 net/socket.c        |    5 +++--
 2 files changed, 3 insertions(+), 6 deletions(-)


Signed-off-by: Adrian Bunk <bunk@stusta.de>

--- linux-2.6.10-rc2-mm4-full/include/linux/net.h.old	2004-12-12 19:03:55.000000000 +0100
+++ linux-2.6.10-rc2-mm4-full/include/linux/net.h	2004-12-12 19:04:01.000000000 +0100
@@ -187,10 +187,6 @@
 				  size_t len);
 extern int	     sock_recvmsg(struct socket *sock, struct msghdr *msg,
 				  size_t size, int flags);
-extern int	     sock_readv_writev(int type, struct inode *inode,
-				       struct file *file,
-				       const struct iovec *iov, long count,
-				       size_t size);
 extern int 	     sock_map_fd(struct socket *sock);
 extern struct socket *sockfd_lookup(int fd, int *err);
 #define		     sockfd_put(sock) fput(sock->file)
--- linux-2.6.10-rc2-mm4-full/net/socket.c.old	2004-12-12 19:04:08.000000000 +0100
+++ linux-2.6.10-rc2-mm4-full/net/socket.c	2004-12-12 19:04:46.000000000 +0100
@@ -736,8 +736,9 @@
 	return sock->ops->sendpage(sock, page, offset, size, flags);
 }
 
-int sock_readv_writev(int type, struct inode * inode, struct file * file,
-		      const struct iovec * iov, long count, size_t size)
+static int sock_readv_writev(int type, struct inode * inode,
+			     struct file * file, const struct iovec * iov,
+			     long count, size_t size)
 {
 	struct msghdr msg;
 	struct socket *sock;


             reply	other threads:[~2004-12-12 21:16 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-12 21:15 Adrian Bunk [this message]
2004-12-28  2:52 ` [2.6 patch] net/socket.c: make a function static 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=20041212211506.GY22324@stusta.de \
    --to=bunk@stusta.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@oss.sgi.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.