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>
Cc: ext2-devel@lists.sourceforge.net, linux-kernel@vger.kernel.org
Subject: Re: [RFC: 2.6 patch] ext2: make ext2_count_free a static inline
Date: Mon, 16 May 2005 20:51:01 +0200	[thread overview]
Message-ID: <20050516185100.GE5112@stusta.de> (raw)
In-Reply-To: <20050513224004.3f68a1e8.akpm@osdl.org>

On Fri, May 13, 2005 at 10:40:04PM -0700, Andrew Morton wrote:
> Adrian Bunk <bunk@stusta.de> wrote:
> >
> >  --- linux-2.6.12-rc2-mm3-full/fs/ext2/ext2.h.old	2005-04-20 23:08:52.000000000 +0200
> >  +++ linux-2.6.12-rc2-mm3-full/fs/ext2/ext2.h	2005-04-20 23:14:21.000000000 +0200
> >  @@ -1,5 +1,6 @@
> >   #include <linux/fs.h>
> >   #include <linux/ext2_fs.h>
> >  +#include <linux/buffer_head.h>
> >   
> >   /*
> >    * second extended file system inode data in memory
> >  @@ -79,6 +80,22 @@
> >   	return container_of(inode, struct ext2_inode_info, vfs_inode);
> >   }
> >   
> >  +static int nibblemap[] = {4, 3, 3, 2, 3, 2, 2, 1, 3, 2, 2, 1, 2, 1, 1, 0};
> >  +
> 
> This will cause a copy of `nibblemap' to be included in each compilation
> unit which uses ext2.h.  Unless the compiler is sufficiently smart to elide
> it, which it might be.  But then it might be sufficiently smart to generate
> a "you're not usig this" warning too.

gcc never generates a warning because it's used in the "static inline" 
function ext2_count_free (whether this function is used or not doesn't 
matter).

But I get your point.

> If it's only needed for EXT2_DEBUG then I'd be inclined to move it into one
> of the other .c files, inside EXT2_DEBUG.  Or just leave it as-is.

Sounds good.

Any suggestion into which file it should be moved?

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-05-16 18:51 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-13  0:47 [RFC: 2.6 patch] ext2: make ext2_count_free a static inline Adrian Bunk
2005-05-14  5:40 ` Andrew Morton
2005-05-16 18:51   ` Adrian Bunk [this message]
2005-11-18  3:33   ` [2.6 patch] fs/ext2/bitmap.c: ext2_count_free() is only required #ifdef EXT2FS_DEBUG Adrian Bunk
  -- strict thread matches above, loose matches on Subject: below --
2005-04-30 20:07 [RFC: 2.6 patch] ext2: make ext2_count_free a static inline Adrian Bunk
2005-04-22 23:51 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=20050516185100.GE5112@stusta.de \
    --to=bunk@stusta.de \
    --cc=akpm@osdl.org \
    --cc=ext2-devel@lists.sourceforge.net \
    --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