The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: David Chamness <chamness@PolyServe.com>
To: linux-kernel@vger.kernel.org
Cc: alan@redhat.com, torvalds@transmeta.com
Subject: [PATCH] minor change to netsyms.c
Date: Wed, 11 Jul 2001 11:01:54 -0700	[thread overview]
Message-ID: <3B4C9492.7070201@PolyServe.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 410 bytes --]

Currently, inet_stream_ops only gets exported if experimental code (IPV6 
module or KHTTPD) is configured.  This patch makes the exporting of 
inet_stream_ops the same as inet_dgram_ops, whenever CONFIG_INET is 
defined.  I have written a module that needs both these symbols 
exported, and it would be much cleaner if they both were exported in a 
consistent manner.

Thanks,
David Chamness
PolyServe, Inc.



[-- Attachment #2: patch-netsyms.c --]
[-- Type: text/plain, Size: 654 bytes --]

--- v2.4.6/linux/net/netsyms.c	Mon Jul  9 11:18:56 2001
+++ linux/net/netsyms.c	Mon Jul  9 11:17:05 2001
@@ -251,6 +251,7 @@
 EXPORT_SYMBOL(ip_mc_inc_group);
 EXPORT_SYMBOL(ip_mc_dec_group);
 EXPORT_SYMBOL(ip_finish_output);
+EXPORT_SYMBOL(inet_stream_ops);
 EXPORT_SYMBOL(inet_dgram_ops);
 EXPORT_SYMBOL(ip_cmsg_recv);
 EXPORT_SYMBOL(inet_addr_type); 
@@ -281,7 +282,6 @@
 #endif
 #if defined (CONFIG_IPV6_MODULE) || defined (CONFIG_KHTTPD) || defined (CONFIG_KHTTPD_MODULE)
 /* inet functions common to v4 and v6 */
-EXPORT_SYMBOL(inet_stream_ops);
 EXPORT_SYMBOL(inet_release);
 EXPORT_SYMBOL(inet_stream_connect);
 EXPORT_SYMBOL(inet_dgram_connect);

             reply	other threads:[~2001-07-11 18:01 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-07-11 18:01 David Chamness [this message]
2001-07-11 23:18 ` [PATCH] minor change to netsyms.c 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=3B4C9492.7070201@PolyServe.com \
    --to=chamness@polyserve.com \
    --cc=alan@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@transmeta.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