From: Stephen Hemminger <shemminger@vyatta.com>
To: Chris Mason <chris.mason@oracle.com>
Cc: linux-btrfs@vger.kernel.org
Subject: namespace routines that could be static
Date: Tue, 28 Sep 2010 17:53:21 +0900 [thread overview]
Message-ID: <20100928175321.3a39280e@s6510> (raw)
I got namespace.pl working again, and it showed the following
routines could be declared static.
fs/btrfs/ctree
btrfs_clear_path_blocking
btrfs_insert_some_items
btrfs_prev_leaf
fs/btrfs/delayed-ref
btrfs_delayed_ref_pending
fs/btrfs/dir-item
btrfs_match_dir_item_name
fs/btrfs/disk-io
btrfs_congested_async
btrfs_lookup_fs_root
btrfs_read_fs_root
write_all_supers
fs/btrfs/extent-tree
block_rsv_release_bytes
btrfs_get_block_group
btrfs_init_new_buffer
fs/btrfs/extent_io
extent_bmap
extent_commit_write
extent_prepare_write
set_range_dirty
wait_extent_bit
wait_on_extent_buffer_writeback
wait_on_extent_writeback
fs/btrfs/file-item
btrfs_lookup_csum
fs/btrfs/free-space-cache
btrfs_block_group_free_space
fs/btrfs/inode
btrfs_orphan_del
btrfs_writepages
fs/btrfs/inode-map
btrfs_find_highest_inode
fs/btrfs/ioctl
btrfs_ioctl_space_info
fs/btrfs/locking
btrfs_try_tree_lock
fs/btrfs/print-tree
btrfs_print_tree
fs/btrfs/root-tree
btrfs_search_root
fs/btrfs/struct-funcs
btrfs_device_bandwidth
btrfs_device_group
btrfs_device_seek_speed
btrfs_device_start_offset
btrfs_dir_transid
btrfs_disk_block_group_chunk_objectid
btrfs_disk_block_group_flags
btrfs_disk_root_generation
btrfs_disk_root_level
btrfs_file_extent_generation
btrfs_inode_transid
btrfs_set_chunk_io_align
btrfs_set_chunk_io_width
btrfs_set_chunk_length
btrfs_set_chunk_num_stripes
btrfs_set_chunk_owner
btrfs_set_chunk_sector_size
btrfs_set_chunk_stripe_len
btrfs_set_chunk_sub_stripes
btrfs_set_chunk_type
btrfs_set_disk_block_group_chunk_objectid
btrfs_set_disk_block_group_flags
btrfs_set_disk_block_group_used
btrfs_set_disk_root_bytenr
btrfs_set_disk_root_generation
btrfs_set_disk_root_level
btrfs_set_disk_root_refs
btrfs_set_extent_refs_v0
btrfs_set_ref_generation_v0
btrfs_set_ref_objectid_v0
btrfs_set_ref_root_v0
btrfs_set_stripe_devid
btrfs_set_stripe_offset
fs/btrfs/sysfs
btrfs_sysfs_add_root
btrfs_sysfs_add_super
btrfs_sysfs_del_root
btrfs_sysfs_del_super
fs/btrfs/tree-log
btrfs_log_inode_parent
fs/btrfs/volumes
btrfs_add_device
btrfs_alloc_dev_extent
btrfs_lock_volumes
btrfs_read_super_device
btrfs_unlock_volumes
btrfs_unplug_page
reply other threads:[~2010-09-28 8:53 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20100928175321.3a39280e@s6510 \
--to=shemminger@vyatta.com \
--cc=chris.mason@oracle.com \
--cc=linux-btrfs@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;
as well as URLs for NNTP newsgroup(s).