From: Ralf Baechle <ralf@linux-mips.org>
To: "David S. Miller" <davem@davemloft.net>, netdev@vger.kernel.org
Subject: [ROSE] Remove useless prototype for rose_remove_neigh().
Date: Sat, 29 Apr 2006 14:25:53 +0100 [thread overview]
Message-ID: <20060429132553.GA31622@linux-mips.org> (raw)
Signed-off-by: Ralf Baechle <ralf@linux-mips.org>
net/rose/rose_route.c | 2 --
1 file changed, 2 deletions(-)
Index: linux-net.git/net/rose/rose_route.c
===================================================================
--- linux-net.git.orig/net/rose/rose_route.c 2006-04-29 14:18:02.000000000 +0100
+++ linux-net.git/net/rose/rose_route.c 2006-04-29 14:18:58.000000000 +0100
@@ -48,8 +48,6 @@ static DEFINE_SPINLOCK(rose_route_list_l
struct rose_neigh *rose_loopback_neigh;
-static void rose_remove_neigh(struct rose_neigh *);
-
/*
* Add a new route to a node, and in the process add the node and the
* neighbour if it is new.
next reply other threads:[~2006-04-29 18:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-29 13:25 Ralf Baechle [this message]
2006-05-04 6:22 ` [ROSE] Remove useless prototype for rose_remove_neigh() 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=20060429132553.GA31622@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=davem@davemloft.net \
--cc=netdev@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 NNTP newsgroup(s).