linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andreas Dilger <adilger@clusterfs.com>
To: Adrian Bunk <bunk@stusta.de>
Cc: Andrew Morton <akpm@osdl.org>,
	sct@redhat.com, linux-kernel@vger.kernel.org,
	ext3-users@redhat.com
Subject: Re: [2.6 patch] fs/jbd/: possible cleanups
Date: Mon, 25 Apr 2005 16:24:16 -0600	[thread overview]
Message-ID: <20050425222416.GX4752@schnapps.adilger.int> (raw)
In-Reply-To: <20050422235717.GI4355@stusta.de>

[-- Attachment #1: Type: text/plain, Size: 1297 bytes --]

On Apr 23, 2005  01:57 +0200, Adrian Bunk wrote:
> This patch contains the following possible cleanups:
> - make needlessly global functions static
> - #if 0 the following unused global functions:
>   - journal.c: __journal_internal_check

>  /* Static check for data structure consistency.  There's no code
>   * invoked --- we'll just get a linker failure if things aren't right.

The comment above this function specifically says no code is generated
here - the purpose of this function is to generate an error if the
journal superblock is the wrong size (e.g. someone adds fields without
updating the padding).

> - remove the following write-only global variable:
>   - journal.c: current_journal

Looks to be debugging only, seems OK to remove.

>   - journal.c: journal_check_used_features

I'm not aware of any current users of journal_check_used_features(), but
the complementary function journal_check_available_features() IS used by
ext3 and I can imagine that if we ever need to add some more journaling
features it would be useful instead of mucking in the journal internals.

>   - journal.c: journal_recover

Looks like the correct API is actually journal_load() so it seems OK to
unexport.

Cheers, Andreas
--
Andreas Dilger
Principal Software Engineer
Cluster File Systems, Inc.


[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

  parent reply	other threads:[~2005-04-25 22:24 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-22 23:57 [2.6 patch] fs/jbd/: possible cleanups Adrian Bunk
2005-04-25 21:50 ` Mark Fasheh
2005-04-25 22:24 ` Andreas Dilger [this message]
2005-04-30 18:26   ` Adrian Bunk
2005-06-14 21:34 Adrian Bunk
2005-07-02 23:51 Adrian Bunk
2005-07-12 20:27 Adrian Bunk
2005-07-12 22:32 ` Andreas Dilger
2005-07-12 22:43   ` Adrian Bunk
2005-07-12 23:05     ` Andreas Dilger

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=20050425222416.GX4752@schnapps.adilger.int \
    --to=adilger@clusterfs.com \
    --cc=akpm@osdl.org \
    --cc=bunk@stusta.de \
    --cc=ext3-users@redhat.com \
    --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 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).