public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Adrian Bunk <bunk@stusta.de>
To: 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: Sat, 30 Apr 2005 20:26:55 +0200	[thread overview]
Message-ID: <20050430182651.GG3571@stusta.de> (raw)
In-Reply-To: <20050425222416.GX4752@schnapps.adilger.int>

On Mon, Apr 25, 2005 at 04:24:16PM -0600, Andreas Dilger wrote:
> 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).

Ah, that's the part I didn't understand about it.

I still don't like this creating an empty global function.

What about moving it into one of the other functions (e.g. 
journal_init)?

>...
> >   - 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.
>...

My patch changes it from a global EXPORT_SYMBOL'ed function to a static 
function.

If ext3 will ever require it undoing my change shouldn't be a problem.

> Cheers, Andreas

cu
Adrian

-- 

       "Is there not promise of rain?" Ling Tan asked suddenly out
        of the darkness. There had been need of rain for many days.
       "Only a promise," Lao Er said.
                                       Pearl S. Buck - Dragon Seed


  reply	other threads:[~2005-04-30 18:27 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
2005-04-30 18:26   ` Adrian Bunk [this message]
  -- strict thread matches above, loose matches on Subject: below --
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=20050430182651.GG3571@stusta.de \
    --to=bunk@stusta.de \
    --cc=akpm@osdl.org \
    --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