public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Mark Fasheh <mark.fasheh@oracle.com>
To: Adrian Bunk <bunk@stusta.de>
Cc: kurt.hackel@oracle.com, ocfs2-devel@oss.oracle.com,
	linux-kernel@vger.kernel.org
Subject: Re: [RFC: 2.6 patch] fs/ocfs2/: remove unused exports
Date: Sat, 15 Apr 2006 20:34:23 -0700	[thread overview]
Message-ID: <20060416033423.GH25194@ca-server1.us.oracle.com> (raw)
In-Reply-To: <20060414113409.GJ4162@stusta.de>

Hi Adrian,
	These are all cluster stack functions and the OCFS2 cluster stack is
pretty much OCFS2 specific right now. So technically one could say they can
all be unexported until used by another related module. I'd rather leave
some of the ones that could make sense as exports though.

On Fri, Apr 14, 2006 at 01:34:09PM +0200, Adrian Bunk wrote:
> This patch removes the following unused EXPORT_SYMBOL_GPL's:
> - cluster/heartbeat.c: o2hb_check_node_heartbeating_from_callback
Completes an API. Lets keep this one please :)

> - cluster/heartbeat.c: o2hb_stop_all_regions
Hmm, called by the quorum stuff, which right now is embedded in the same
module as heartbeat anyway. Can probably go.

> - cluster/nodemanager.c: o2nm_get_node_by_num
> - cluster/nodemanager.c: o2nm_configured_node_map
> - cluster/nodemanager.c: o2nm_get_node_by_ip
I could definitely see the file system using these.

> - cluster/nodemanager.c: o2nm_node_put
> - cluster/nodemanager.c: o2nm_node_get
Can go for now.

> - dlm/dlmmaster.c: dlm_migrate_lockres
Was exported for debugging only anyway AFAIR. Can go.

Thanks,
	--Mark

--
Mark Fasheh
Senior Software Developer, Oracle
mark.fasheh@oracle.com


      reply	other threads:[~2006-04-16  3:37 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-14 11:34 [RFC: 2.6 patch] fs/ocfs2/: remove unused exports Adrian Bunk
2006-04-16  3:34 ` Mark Fasheh [this message]

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=20060416033423.GH25194@ca-server1.us.oracle.com \
    --to=mark.fasheh@oracle.com \
    --cc=bunk@stusta.de \
    --cc=kurt.hackel@oracle.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ocfs2-devel@oss.oracle.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