From: Roman Zippel <zippel@linux-m68k.org>
To: Adrian Bunk <bunk@stusta.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [2.6 patch] fs/hfsplus/: misc cleanups
Date: Fri, 7 Jan 2005 16:23:46 +0100 [thread overview]
Message-ID: <200501071623.48201.zippel@linux-m68k.org> (raw)
In-Reply-To: <20050107012615.GB14108@stusta.de>
Hi,
On Friday 07 January 2005 02:26, Adrian Bunk wrote:
> +#define hfs_bnode_split hfsplus_bnode_split
> +static struct hfs_bnode *hfs_bnode_split(struct hfs_find_data *fd);
> +
> +#define hfs_brec_update_parent hfsplus_brec_update_parent
> +static int hfs_brec_update_parent(struct hfs_find_data *fd);
> +
> +#define hfs_btree_inc_height hfsplus_btree_inc_height
> +static int hfs_btree_inc_height(struct hfs_btree *);
If these functions become static, the defines are not needed anymore. This
code is "shared" with hfs and only kernel wide visible functions are renamed
this way.
bye, Roman
next prev parent reply other threads:[~2005-01-07 18:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-07 1:26 [2.6 patch] fs/hfsplus/: misc cleanups Adrian Bunk
2005-01-07 15:23 ` Roman Zippel [this message]
2005-01-08 1:29 ` Adrian Bunk
-- strict thread matches above, loose matches on Subject: below --
2005-01-31 23:42 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=200501071623.48201.zippel@linux-m68k.org \
--to=zippel@linux-m68k.org \
--cc=bunk@stusta.de \
--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