On Wed, Aug 7, 2013 at 7:38 AM, Stephen Rothwell <[email protected]> wrote: > Hi Sedat, > > On Wed, 7 Aug 2013 07:16:57 +0200 Sedat Dilek > <[email protected]> wrote: >> >> On Mon, Jul 29, 2013 at 3:08 AM, Stephen Rothwell <[email protected]> >> wrote: >> > >> > After merging the ext4 tree, today's linux-next build (powerpc >> > ppc64_defconfig) failed like this: >> > >> > fs/ext4/ialloc.c: In function '__ext4_new_inode': >> > fs/ext4/ialloc.c:817:1: warning: label 'next_ino' defined but not used >> > [-Wunused-label] >> > next_ino: >> > ^ >> > fs/ext4/ialloc.c:792:4: error: label 'next_inode' used but not defined >> > goto next_inode; >> > ^ >> > >> > Hmm ... >> > >> > Caused by commit 4a8603ef197a ("ext4: avoid reusing recently deleted >> > inodes in no journal mode"). >> > >> > I have used the ext4 tree from next-20130726 for today. >> >> Since this message ext4-tree was not updated. >> The commit "ext4: avoid reusing recently deleted inodes in no journal >> mode" was refreshed and has a different commit-id. >> Did you test with this one? You still see the breakage? > > Today's linux-next does not have this build failure.
The refreshed patch is from 02-Aug-2013. So why did next-20130805 and next-20130806 did not have it? I was reading for these Linux-next releases the same: "I have used the ext4 tree from next-20130726 for today.". I am wondering what went wrong. - Sedat - > -- > Cheers, > Stephen Rothwell [email protected] -- 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/
