* [PATCH net-next-2.6] gro: unexport tcp4_gro_receive and tcp4_gro_complete
@ 2010-08-31 20:23 Eric Dumazet
2010-08-31 20:33 ` David Miller
0 siblings, 1 reply; 2+ messages in thread
From: Eric Dumazet @ 2010-08-31 20:23 UTC (permalink / raw)
To: David Miller; +Cc: netdev
tcp4_gro_receive() and tcp4_gro_complete() dont need to be exported.
Signed-off-by: Eric Dumazet <eric.dumazet@gmail.com>
---
net/ipv4/tcp_ipv4.c | 2 --
1 file changed, 2 deletions(-)
diff --git a/net/ipv4/tcp_ipv4.c b/net/ipv4/tcp_ipv4.c
index 0207662..a0232f3 100644
--- a/net/ipv4/tcp_ipv4.c
+++ b/net/ipv4/tcp_ipv4.c
@@ -2571,7 +2571,6 @@ struct sk_buff **tcp4_gro_receive(struct sk_buff **head, struct sk_buff *skb)
return tcp_gro_receive(head, skb);
}
-EXPORT_SYMBOL(tcp4_gro_receive);
int tcp4_gro_complete(struct sk_buff *skb)
{
@@ -2584,7 +2583,6 @@ int tcp4_gro_complete(struct sk_buff *skb)
return tcp_gro_complete(skb);
}
-EXPORT_SYMBOL(tcp4_gro_complete);
struct proto tcp_prot = {
.name = "TCP",
^ permalink raw reply related [flat|nested] 2+ messages in thread
* Re: [PATCH net-next-2.6] gro: unexport tcp4_gro_receive and tcp4_gro_complete
2010-08-31 20:23 [PATCH net-next-2.6] gro: unexport tcp4_gro_receive and tcp4_gro_complete Eric Dumazet
@ 2010-08-31 20:33 ` David Miller
0 siblings, 0 replies; 2+ messages in thread
From: David Miller @ 2010-08-31 20:33 UTC (permalink / raw)
To: eric.dumazet; +Cc: netdev
From: Eric Dumazet <eric.dumazet@gmail.com>
Date: Tue, 31 Aug 2010 22:23:47 +0200
> tcp4_gro_receive() and tcp4_gro_complete() dont need to be exported.
>
> Signed-off-by: Eric Dumazet <eric.dumazet@gmail.com>
Looks good, I'll apply this.
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2010-08-31 20:33 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2010-08-31 20:23 [PATCH net-next-2.6] gro: unexport tcp4_gro_receive and tcp4_gro_complete Eric Dumazet
2010-08-31 20:33 ` David Miller
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).