From: Christoph Hellwig <hch@lst.de>
To: xfs@oss.sgi.com
Subject: Re: [PATCH] remove exports of inline functions
Date: Wed, 15 Oct 2008 12:48:40 +0200 [thread overview]
Message-ID: <20081015104840.GA8853@lst.de> (raw)
In-Reply-To: <20081006181626.GA15388@lst.de>
On Mon, Oct 06, 2008 at 08:16:26PM +0200, Christoph Hellwig wrote:
> Recent gcc starts to complain about exports of functions marked static
> inline, so let's get rid of those.
note that the complain is in the form of a kernel doesn't link, so any
chance we could get this patch in?
>
>
> Signed-off-by: Christoph Hellwig <hch@lst.de>
>
> Index: linux-2.6-xfs/fs/xfs/linux-2.6/xfs_ksyms.c
> ===================================================================
> --- linux-2.6-xfs.orig/fs/xfs/linux-2.6/xfs_ksyms.c 2008-10-07 01:08:33.000000000 +0000
> +++ linux-2.6-xfs/fs/xfs/linux-2.6/xfs_ksyms.c 2008-10-07 01:09:58.000000000 +0000
> @@ -153,8 +153,6 @@
> EXPORT_SYMBOL(kmem_zalloc);
> EXPORT_SYMBOL(kmem_zone_alloc);
> EXPORT_SYMBOL(kmem_zalloc_greedy);
> -EXPORT_SYMBOL(kmem_zone_free);
> -EXPORT_SYMBOL(kmem_zone_init);
> EXPORT_SYMBOL(kmem_zone_zalloc);
> EXPORT_SYMBOL(xfs_address_space_operations);
> EXPORT_SYMBOL(xfs_dir_file_operations);
> @@ -217,8 +215,6 @@
> EXPORT_SYMBOL(xfs_finish_reclaim_all);
> EXPORT_SYMBOL(xfs_freesb);
> EXPORT_SYMBOL(xfs_fs_cmn_err);
> -EXPORT_SYMBOL(xfs_highbit32);
> -EXPORT_SYMBOL(xfs_highbit64);
> EXPORT_SYMBOL(xfs_idestroy);
> EXPORT_SYMBOL(xfs_iextract);
> EXPORT_SYMBOL(xfs_iext_add);
> @@ -227,10 +223,7 @@
> EXPORT_SYMBOL(xfs_iext_idx_to_irec);
> EXPORT_SYMBOL(xfs_iext_insert);
> EXPORT_SYMBOL(xfs_iext_remove);
> -EXPORT_SYMBOL(xfs_iflock);
> -EXPORT_SYMBOL(xfs_iflock_nowait);
> EXPORT_SYMBOL(xfs_iflush);
> -EXPORT_SYMBOL(xfs_ifunlock);
> EXPORT_SYMBOL(xfs_iget);
> EXPORT_SYMBOL(xfs_ilock);
> EXPORT_SYMBOL(xfs_ilock_map_shared);
---end quoted text---
next prev parent reply other threads:[~2008-10-15 10:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-06 18:16 [PATCH] remove exports of inline functions Christoph Hellwig
2008-10-15 10:48 ` Christoph Hellwig [this message]
2008-10-16 0:19 ` Donald Douwsma
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=20081015104840.GA8853@lst.de \
--to=hch@lst.de \
--cc=xfs@oss.sgi.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