public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg Stark <gsstark@mit.edu>
To: linux-kernel@vger.kernel.org
Subject: 2.6.11 breaks modules gratuitously
Date: 18 Mar 2005 10:33:29 -0500	[thread overview]
Message-ID: <87fyythsty.fsf@stark.xeocode.com> (raw)


When you guys go on these "make needlessly global code static" kicks you
should maybe consider that even functions that aren't currently used by any
other area of the tree might be useful for module writers.

Instead of just checking which functions are currently used by other parts of
the kernel perhaps you should think about what makes a logical API and stick
to that, even if not all of the functions are currently used.

In the case of net/core/datagram.c, why make skb_copy_datagram private but
leave skb_copy_datagram_iovec global? If the latter is a useful public
function why not the former?

In particular vmware used skb_copy_datagram. So 2.6.11 broke vmware for no
good reason.



<bunk@stusta.de>
	[NET]: misc cleanups
	
	The patch below contains the following cleanups:
	- make needlessly global code static
	- remove the following unused global functions:
	  - datagram.c: skb_copy_datagram
	  - iovec.c: memcpy_tokerneliovec
	- remove the following unneeded EXPORT_SYMBOL's:
	  - datagram.c: skb_copy_datagram
	  - dev.c: ing_filter
	  - iovec.c: memcpy_tokerneliovec
	  - netpoll.c: netpoll_send_skb
	  - rtnetlink.c: rtnetlink_dump_ifinfo
	  - sock.c: sock_alloc_send_pskb
	
	Signed-off-by: Adrian Bunk <bunk@stusta.de>
	Signed-off-by: David S. Miller <davem@davemloft.net>


-- 
greg


             reply	other threads:[~2005-03-18 15:40 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-18 15:33 Greg Stark [this message]
2005-03-18 16:00 ` 2.6.11 breaks modules gratuitously Ian Campbell
     [not found] <3JrTO-1C4-41@gated-at.bofh.it>
2005-03-18 18:49 ` Jean Delvare
2005-03-18 19:01   ` John Kacur
2005-03-18 19:14     ` Adrian Bunk

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=87fyythsty.fsf@stark.xeocode.com \
    --to=gsstark@mit.edu \
    --cc=linux-kernel@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