2.6.13-rc6-mm1: git-ocfs2.patch breaks jffs

2005-08-20 Thread Adrian Bunk
On Fri, Aug 19, 2005 at 04:33:31AM -0700, Andrew Morton wrote:
>...
> Changes since 2.6.13-rc5-mm1:
>...
>  git-ocfs2.patch
>...
>  Subsystem trees
>...

gcc correctly tells that at least a part of this patch incorrect (not 
that gcc says "is used", not "might be used"):

<--  snip  -->

...
  CC  fs/jffs/inode-v23.o
fs/jffs/inode-v23.c: In function 'jffs_create':
fs/jffs/inode-v23.c:1282: warning: 'inode' is used uninitialized in this 
function
...

<--  snip  -->

Looking at the code, it's trivial to verify that gcc is right.

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

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/


2.6.13-rc6-mm1: git-ocfs2.patch breaks jffs

2005-08-20 Thread Adrian Bunk
On Fri, Aug 19, 2005 at 04:33:31AM -0700, Andrew Morton wrote:
...
 Changes since 2.6.13-rc5-mm1:
...
  git-ocfs2.patch
...
  Subsystem trees
...

gcc correctly tells that at least a part of this patch incorrect (not 
that gcc says is used, not might be used):

--  snip  --

...
  CC  fs/jffs/inode-v23.o
fs/jffs/inode-v23.c: In function 'jffs_create':
fs/jffs/inode-v23.c:1282: warning: 'inode' is used uninitialized in this 
function
...

--  snip  --

Looking at the code, it's trivial to verify that gcc is right.

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

-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/