From: "Sébastien Barré" <sebastien.barre@uclouvain.be>
To: "David S. Miller" <davem@davemloft.net>
Cc: "Sébastien Barré" <sebastien.barre@uclouvain.be>,
"Vlad Yasevich" <vyasevich@gmail.com>,
"Neil Horman" <nhorman@tuxdriver.com>,
linux-sctp@vger.kernel.org, netdev@vger.kernel.org
Subject: [PATCH net-next] Removed unused function sctp_addr_is_valid()
Date: Tue, 21 Oct 2014 15:26:15 +0200 [thread overview]
Message-ID: <1413897975-6066-1-git-send-email-sebastien.barre@uclouvain.be> (raw)
sctp_addr_is_valid() only appeared in its definition.
Acked-by: Neil Horman <nhorman@tuxdriver.com>
Signed-off-by: Sébastien Barré <sebastien.barre@uclouvain.be>
---
Note: originally sent on linux-sctp (11/10/2014, 16:29).
Sorry, I should probably have sent immediately to you and netdev as well.
Neil Horman had acked the patch, so I included
the ack here.
include/net/sctp/structs.h | 1 -
1 file changed, 1 deletion(-)
diff --git a/include/net/sctp/structs.h b/include/net/sctp/structs.h
index 4ff3f67..806e3b5 100644
--- a/include/net/sctp/structs.h
+++ b/include/net/sctp/structs.h
@@ -1116,7 +1116,6 @@ int sctp_raw_to_bind_addrs(struct sctp_bind_addr *bp, __u8 *raw, int len,
sctp_scope_t sctp_scope(const union sctp_addr *);
int sctp_in_scope(struct net *net, const union sctp_addr *addr, const sctp_scope_t scope);
int sctp_is_any(struct sock *sk, const union sctp_addr *addr);
-int sctp_addr_is_valid(const union sctp_addr *addr);
int sctp_is_ep_boundall(struct sock *sk);
--
tg: (61ed53d..) net-next/removed-unused-sctp-function (depends on: net-next/master)
next reply other threads:[~2014-10-21 13:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-21 13:26 Sébastien Barré [this message]
2014-10-24 4:37 ` [PATCH net-next] Removed unused function sctp_addr_is_valid() David 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=1413897975-6066-1-git-send-email-sebastien.barre@uclouvain.be \
--to=sebastien.barre@uclouvain.be \
--cc=davem@davemloft.net \
--cc=linux-sctp@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=nhorman@tuxdriver.com \
--cc=vyasevich@gmail.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 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).