From: Andreas Dilger <adilger@sun.com>
To: Adrian Bunk <bunk@kernel.org>
Cc: sct@redhat.com, akpm@linux-foundation.org,
linux-ext4@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [2.6 patch] fs/jbd/journal.c: cleanups
Date: Mon, 18 Feb 2008 00:04:39 -0700 [thread overview]
Message-ID: <20080218070439.GG3029@webber.adilger.int> (raw)
In-Reply-To: <20080217081935.GN3848@cs181133002.pp.htv.fi>
On Feb 17, 2008 10:19 +0200, Adrian Bunk wrote:
> This patch contains the following cleanups:
> - make the following needlessly global function static:
> - journal_check_used_features()
> - remove the following unused EXPORT_SYMBOL's:
> - journal_set_features
> - journal_update_superblock
Nack. I don't object to un-exporting journal_update_superblock(), because
that is pretty internal, but the other functions are intended specifically
for use by code outside of JBD. For example, the journal checksum patch for
ext3/4 uses journal_set_features() to turn on features in the JBD superblock.
Similarly, for 64-bit support in ext4 uses journal_set_features() to set
a 64-bit feature flag in the journal superblock.
Cheers, Andreas
--
Andreas Dilger
Sr. Staff Engineer, Lustre Group
Sun Microsystems of Canada, Inc.
next prev parent reply other threads:[~2008-02-18 7:04 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-17 8:19 [2.6 patch] fs/jbd/journal.c: cleanups Adrian Bunk
2008-02-18 7:04 ` Andreas Dilger [this message]
2008-02-18 7:12 ` Ingo Molnar
2008-02-18 11:49 ` Theodore Tso
2008-02-18 12:57 ` Ingo Molnar
2008-02-18 12:57 ` Ingo Molnar
2008-02-18 13:31 ` Theodore Tso
2008-02-18 13:55 ` Ingo Molnar
2008-02-18 13:55 ` Ingo Molnar
2008-02-18 13:12 ` Adrian Bunk
2008-02-18 13:28 ` Theodore Tso
2008-02-27 19:39 ` Adrian Bunk
2008-02-18 13:31 ` Ingo Molnar
2008-02-18 15:11 ` Theodore Tso
2008-02-18 16:22 ` Ingo Molnar
2008-02-18 16:22 ` Ingo Molnar
2008-02-27 21:20 ` [2.6 patch] unexport journal_update_superblock 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=20080218070439.GG3029@webber.adilger.int \
--to=adilger@sun.com \
--cc=akpm@linux-foundation.org \
--cc=bunk@kernel.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sct@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.