On Tue, Oct 09, 2018 at 10:51:02AM +1100, Stephen Rothwell wrote:
> Hi Ted,
>
> After merging the ext4 tree, today's linux-next build (arm
> multi_v7_defconfig) failed like this:
Oops, my bad. Thanks for catching this. I failed to a new helper
function inside #ifdef CONFIG_QUOTA .. #endif.
On Tue, Oct 09, 2018 at 10:51:02AM +1100, Stephen Rothwell wrote:
> Hi Ted,
>
> After merging the ext4 tree, today's linux-next build (arm
> multi_v7_defconfig) failed like this:
Oops, my bad. Thanks for catching this. I failed to a new helper
function inside #ifdef CONFIG_QUOTA .. #endif.
Hi Ted,
After merging the ext4 tree, today's linux-next build (arm
multi_v7_defconfig) failed like this:
In file included from include/linux/srcu.h:33,
from include/linux/notifier.h:16,
from include/linux/memory_hotplug.h:7,
from
Hi Ted,
After merging the ext4 tree, today's linux-next build (arm
multi_v7_defconfig) failed like this:
In file included from include/linux/srcu.h:33,
from include/linux/notifier.h:16,
from include/linux/memory_hotplug.h:7,
from
Hi Ted,
After merging the ext4 tree, today's linux-next build (arm
multi_v7_defconfig) failed like this:
fs/ext4/namei.c: In function 'ext4_lookup':
fs/ext4/namei.c:1572:24: error: 'struct ext4_inode_info' has no member named
'i_crypt_info'
if (EXT4_I(dir)->i_crypt_info == NULL)
Hi Ted,
After merging the ext4 tree, today's linux-next build (arm
multi_v7_defconfig) failed like this:
fs/ext4/namei.c: In function 'ext4_lookup':
fs/ext4/namei.c:1572:24: error: 'struct ext4_inode_info' has no member named
'i_crypt_info'
if (EXT4_I(dir)->i_crypt_info == NULL)
On Mon, Jan 04, 2016 at 10:34:19AM +1100, Stephen Rothwell wrote:
> Hi Ted,
>
> After merging the ext4 tree, today's linux-next build (arm
> multi_v7_defconfig) failed like this:...
Thanks for pointing this out! I fixed it last night so it should be
ready for the next linux-build integration
On Mon, Jan 04, 2016 at 10:34:19AM +1100, Stephen Rothwell wrote:
> Hi Ted,
>
> After merging the ext4 tree, today's linux-next build (arm
> multi_v7_defconfig) failed like this:...
Thanks for pointing this out! I fixed it last night so it should be
ready for the next linux-build integration
Hi Ted,
After merging the ext4 tree, today's linux-next build (arm
multi_v7_defconfig) failed like this:
fs/ext4/ioctl.c: In function 'ext4_ioctl_setproject':
fs/ext4/ioctl.c:399:26: error: implicit declaration of function 'dqget'
[-Werror=implicit-function-declaration]
transfer_to[PRJQUOTA]
Hi Ted,
After merging the ext4 tree, today's linux-next build (arm
multi_v7_defconfig) failed like this:
fs/ext4/ioctl.c: In function 'ext4_ioctl_setproject':
fs/ext4/ioctl.c:399:26: error: implicit declaration of function 'dqget'
[-Werror=implicit-function-declaration]
transfer_to[PRJQUOTA]
On Thu, Jul 23, 2015 at 01:23:43PM -0400, Theodore Ts'o wrote:
> On Thu, Jul 23, 2015 at 12:49:53PM -0400, Theodore Ts'o wrote:
> > > After merging the ext4 tree, today's linux-next build (x86_64
> > > allmodconfig) failed like this:
> > >
> > > ERROR: "wbc_account_io" [fs/ext4/ext4.ko]
On Thu, Jul 23, 2015 at 12:49:53PM -0400, Theodore Ts'o wrote:
> > After merging the ext4 tree, today's linux-next build (x86_64
> > allmodconfig) failed like this:
> >
> > ERROR: "wbc_account_io" [fs/ext4/ext4.ko] undefined!
> > ERROR: "bio_associate_blkcg" [fs/ext4/ext4.ko] undefined!
> >
> >
On Thu, Jul 23, 2015 at 10:56:23AM +1000, Stephen Rothwell wrote:
> Hi Theodore,
>
> After merging the ext4 tree, today's linux-next build (x86_64
> allmodconfig) failed like this:
>
> ERROR: "wbc_account_io" [fs/ext4/ext4.ko] undefined!
> ERROR: "bio_associate_blkcg" [fs/ext4/ext4.ko]
On Thu, Jul 23, 2015 at 12:49:53PM -0400, Theodore Ts'o wrote:
After merging the ext4 tree, today's linux-next build (x86_64
allmodconfig) failed like this:
ERROR: wbc_account_io [fs/ext4/ext4.ko] undefined!
ERROR: bio_associate_blkcg [fs/ext4/ext4.ko] undefined!
Caused by commit
On Thu, Jul 23, 2015 at 01:23:43PM -0400, Theodore Ts'o wrote:
On Thu, Jul 23, 2015 at 12:49:53PM -0400, Theodore Ts'o wrote:
After merging the ext4 tree, today's linux-next build (x86_64
allmodconfig) failed like this:
ERROR: wbc_account_io [fs/ext4/ext4.ko] undefined!
ERROR:
On Thu, Jul 23, 2015 at 10:56:23AM +1000, Stephen Rothwell wrote:
Hi Theodore,
After merging the ext4 tree, today's linux-next build (x86_64
allmodconfig) failed like this:
ERROR: wbc_account_io [fs/ext4/ext4.ko] undefined!
ERROR: bio_associate_blkcg [fs/ext4/ext4.ko] undefined!
Caused
Hi Theodore,
After merging the ext4 tree, today's linux-next build (x86_64
allmodconfig) failed like this:
ERROR: "wbc_account_io" [fs/ext4/ext4.ko] undefined!
ERROR: "bio_associate_blkcg" [fs/ext4/ext4.ko] undefined!
Caused by commit
001e4a8775f6 ("ext4: implement cgroup writeback support")
Hi Theodore,
After merging the ext4 tree, today's linux-next build (x86_64
allmodconfig) failed like this:
ERROR: wbc_account_io [fs/ext4/ext4.ko] undefined!
ERROR: bio_associate_blkcg [fs/ext4/ext4.ko] undefined!
Caused by commit
001e4a8775f6 (ext4: implement cgroup writeback support)
I
Hi Ted,
After merging the ext4 tree, today's linux-next build (powerpc
ppc64_defconfig) failed like this:
fs/ext4/file.c: In function 'ext4_file_mmap':
fs/ext4/file.c:226:3: error: implicit declaration of function
'ext4_get_encryption_info' [-Werror=implicit-function-declaration]
int err =
Hi Ted,
After merging the ext4 tree, today's linux-next build (powerpc
ppc64_defconfig) failed like this:
fs/ext4/file.c: In function 'ext4_file_mmap':
fs/ext4/file.c:226:3: error: implicit declaration of function
'ext4_get_encryption_info' [-Werror=implicit-function-declaration]
int err =
Sam, Michal, All,
On 2013-08-16 19:14 +0200, Sam Ravnborg spake thusly:
> On Fri, Aug 16, 2013 at 03:10:38PM +0200, Michal Marek wrote:
> > On 11.8.2013 23:39, Yann E. MORIN wrote:
> > > On 2013-08-09 13:42 +0200, Sam Ravnborg spake thusly:
> > >> If we drop the special handling of "MODULES" and
On Fri, Aug 16, 2013 at 03:10:38PM +0200, Michal Marek wrote:
> On 11.8.2013 23:39, Yann E. MORIN wrote:
> > On 2013-08-09 13:42 +0200, Sam Ravnborg spake thusly:
> >> If we drop the special handling of "MODULES" and introduced
> >> the following in we may fix it - hopefully:
> >>
> >> config
On 11.8.2013 23:39, Yann E. MORIN wrote:
> On 2013-08-09 13:42 +0200, Sam Ravnborg spake thusly:
>> If we drop the special handling of "MODULES" and introduced
>> the following in we may fix it - hopefully:
>>
>> config MODULES
>> option modules
>>
>> The option handling is already in place.
On 11.8.2013 23:39, Yann E. MORIN wrote:
On 2013-08-09 13:42 +0200, Sam Ravnborg spake thusly:
If we drop the special handling of MODULES and introduced
the following in we may fix it - hopefully:
config MODULES
option modules
The option handling is already in place. It is even
On Fri, Aug 16, 2013 at 03:10:38PM +0200, Michal Marek wrote:
On 11.8.2013 23:39, Yann E. MORIN wrote:
On 2013-08-09 13:42 +0200, Sam Ravnborg spake thusly:
If we drop the special handling of MODULES and introduced
the following in we may fix it - hopefully:
config MODULES
option
Sam, Michal, All,
On 2013-08-16 19:14 +0200, Sam Ravnborg spake thusly:
On Fri, Aug 16, 2013 at 03:10:38PM +0200, Michal Marek wrote:
On 11.8.2013 23:39, Yann E. MORIN wrote:
On 2013-08-09 13:42 +0200, Sam Ravnborg spake thusly:
If we drop the special handling of MODULES and introduced
Sam, All,
On 2013-08-09 13:42 +0200, Sam Ravnborg spake thusly:
> On Thu, Aug 08, 2013 at 11:54:49PM +0200, Yann E. MORIN wrote:
> > Stephen, All,
> >
> > On 2013-08-08 21:16 +0200, Yann E. MORIN spake thusly:
> > > On 2013-08-08 10:36 +1000, Stephen Rothwell spake thusly:
> > > > On Thu, 8 Aug
Sam, All,
On 2013-08-09 13:42 +0200, Sam Ravnborg spake thusly:
On Thu, Aug 08, 2013 at 11:54:49PM +0200, Yann E. MORIN wrote:
Stephen, All,
On 2013-08-08 21:16 +0200, Yann E. MORIN spake thusly:
On 2013-08-08 10:36 +1000, Stephen Rothwell spake thusly:
On Thu, 8 Aug 2013 10:22:28
On Thu, Aug 08, 2013 at 11:54:49PM +0200, Yann E. MORIN wrote:
> Stephen, All,
>
> On 2013-08-08 21:16 +0200, Yann E. MORIN spake thusly:
> > On 2013-08-08 10:36 +1000, Stephen Rothwell spake thusly:
> > > On Thu, 8 Aug 2013 10:22:28 +1000 Stephen Rothwell
> > > wrote:
> > > >
> > > > More quick
On Thu, Aug 08, 2013 at 11:54:49PM +0200, Yann E. MORIN wrote:
Stephen, All,
On 2013-08-08 21:16 +0200, Yann E. MORIN spake thusly:
On 2013-08-08 10:36 +1000, Stephen Rothwell spake thusly:
On Thu, 8 Aug 2013 10:22:28 +1000 Stephen Rothwell s...@canb.auug.org.au
wrote:
More
Hi Yann,
On Thu, 8 Aug 2013 23:54:49 +0200 "Yann E. MORIN"
wrote:
>
> Ok, I've had a look in the linux-next archives, and I think I got it.
> Is the following right?
>
> git clean -d; git clean -dX # To be sure tree is clean
> touch empty
> make KCONFIG_ALLCONFIG=empty
Stephen, All,
On 2013-08-08 21:16 +0200, Yann E. MORIN spake thusly:
> On 2013-08-08 10:36 +1000, Stephen Rothwell spake thusly:
> > On Thu, 8 Aug 2013 10:22:28 +1000 Stephen Rothwell
> > wrote:
> > >
> > > More quick testing with an empty file: v3.9 is OK, v3.10 gives
> > > CONFIG_MODULES
Stephen, All,
On 2013-08-08 10:36 +1000, Stephen Rothwell spake thusly:
> On Thu, 8 Aug 2013 10:22:28 +1000 Stephen Rothwell
> wrote:
> >
> > More quick testing with an empty file: v3.9 is OK, v3.10 gives
> > CONFIG_MODULES unset.
Sorry, I don't understand the above. Can you elaborate on what
Stephen, All,
On 2013-08-08 10:36 +1000, Stephen Rothwell spake thusly:
On Thu, 8 Aug 2013 10:22:28 +1000 Stephen Rothwell s...@canb.auug.org.au
wrote:
More quick testing with an empty file: v3.9 is OK, v3.10 gives
CONFIG_MODULES unset.
Sorry, I don't understand the above. Can you
Stephen, All,
On 2013-08-08 21:16 +0200, Yann E. MORIN spake thusly:
On 2013-08-08 10:36 +1000, Stephen Rothwell spake thusly:
On Thu, 8 Aug 2013 10:22:28 +1000 Stephen Rothwell s...@canb.auug.org.au
wrote:
More quick testing with an empty file: v3.9 is OK, v3.10 gives
Hi Yann,
On Thu, 8 Aug 2013 23:54:49 +0200 Yann E. MORIN yann.morin.1...@free.fr
wrote:
Ok, I've had a look in the linux-next archives, and I think I got it.
Is the following right?
git clean -d; git clean -dX # To be sure tree is clean
touch empty
make
On Thu, 8 Aug 2013 10:22:28 +1000 Stephen Rothwell
wrote:
>
> More quick testing with an empty file: v3.9 is OK, v3.10 gives
> CONFIG_MODULES unset.
Bisecting gives:
cfa98f2e0ae956feca935573e977d7661a9561b9 is the first bad commit
commit cfa98f2e0ae956feca935573e977d7661a9561b9
Author: Yann E.
Hi Kevin,
On Wed, 07 Aug 2013 08:28:35 -0700 Kevin Hilman
wrote:
>
> However, this same commit does introduce a new build failure (not
> present in next-20130806) when ext4 is built as a module:
>
> ERROR: "dirty_expire_interval" [fs/ext4/ext4.ko] undefined!
> make[3]: *** [__modpost] Error 1
>
Stephen Rothwell writes:
> Hi Sedat,
>
> On Wed, 7 Aug 2013 07:16:57 +0200 Sedat Dilek
> wrote:
>>
>> On Mon, Jul 29, 2013 at 3:08 AM, Stephen Rothwell
>> wrote:
>> >
>> > After merging the ext4 tree, today's linux-next build (powerpc
>> > ppc64_defconfig) failed like this:
>> >
>> >
Hi Sedat,
On Wed, 7 Aug 2013 07:43:59 +0200 Sedat Dilek
wrote:
>
> 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
Hi Sedat,
On Wed, 7 Aug 2013 07:43:59 +0200 Sedat Dilek
sedat.di...@gmail.com wrote:
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
Stephen Rothwell s...@canb.auug.org.au writes:
Hi Sedat,
On Wed, 7 Aug 2013 07:16:57 +0200 Sedat Dilek
sedat.di...@gmail.com wrote:
On Mon, Jul 29, 2013 at 3:08 AM, Stephen Rothwell s...@canb.auug.org.au
wrote:
After merging the ext4 tree, today's linux-next build (powerpc
Hi Kevin,
On Wed, 07 Aug 2013 08:28:35 -0700 Kevin Hilman
khil...@linaro.org wrote:
However, this same commit does introduce a new build failure (not
present in next-20130806) when ext4 is built as a module:
ERROR: dirty_expire_interval [fs/ext4/ext4.ko] undefined!
make[3]: *** [__modpost]
On Thu, 8 Aug 2013 10:22:28 +1000 Stephen Rothwell s...@canb.auug.org.au
wrote:
More quick testing with an empty file: v3.9 is OK, v3.10 gives
CONFIG_MODULES unset.
Bisecting gives:
cfa98f2e0ae956feca935573e977d7661a9561b9 is the first bad commit
commit
On Wed, Aug 7, 2013 at 7:38 AM, Stephen Rothwell wrote:
> Hi Sedat,
>
> On Wed, 7 Aug 2013 07:16:57 +0200 Sedat Dilek
> wrote:
>>
>> On Mon, Jul 29, 2013 at 3:08 AM, Stephen Rothwell
>> wrote:
>> >
>> > After merging the ext4 tree, today's linux-next build (powerpc
>> > ppc64_defconfig) failed
Hi Sedat,
On Wed, 7 Aug 2013 07:16:57 +0200 Sedat Dilek
wrote:
>
> On Mon, Jul 29, 2013 at 3:08 AM, Stephen Rothwell
> 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':
On Mon, Jul 29, 2013 at 3:08 AM, Stephen Rothwell wrote:
> Hi Theodore,
>
> 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
On Mon, Jul 29, 2013 at 3:08 AM, Stephen Rothwell s...@canb.auug.org.au wrote:
Hi Theodore,
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'
Hi Sedat,
On Wed, 7 Aug 2013 07:16:57 +0200 Sedat Dilek
sedat.di...@gmail.com wrote:
On Mon, Jul 29, 2013 at 3:08 AM, Stephen Rothwell s...@canb.auug.org.au
wrote:
After merging the ext4 tree, today's linux-next build (powerpc
ppc64_defconfig) failed like this:
fs/ext4/ialloc.c: In
On Wed, Aug 7, 2013 at 7:38 AM, Stephen Rothwell s...@canb.auug.org.au wrote:
Hi Sedat,
On Wed, 7 Aug 2013 07:16:57 +0200 Sedat Dilek
sedat.di...@gmail.com wrote:
On Mon, Jul 29, 2013 at 3:08 AM, Stephen Rothwell s...@canb.auug.org.au
wrote:
After merging the ext4 tree, today's
Hi Ted,
On Mon, 29 Jul 2013 11:08:16 +1000 Stephen Rothwell
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
Hi Ted,
On Mon, 29 Jul 2013 11:08:16 +1000 Stephen Rothwell s...@canb.auug.org.au
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'
Hi Theodore,
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:
Hi Theodore,
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:
On Thu, 4 Apr 2013, Theodore Ts'o wrote:
> Date: Thu, 4 Apr 2013 09:20:48 -0400
> From: Theodore Ts'o
> To: Lukáš Czerner
> Cc: Stephen Rothwell , linux-n...@vger.kernel.org,
> linux-kernel@vger.kernel.org
> Subject: Re: linux-next: build failure after merge of the ext
On Thu, Apr 04, 2013 at 03:18:32PM +0200, Lukáš Czerner wrote:
> I am afraid I do not understand why this is happening. The commit
> simply replaces ext4_get_group_no_and_offset() with
> ext4_get_group_number() which has the similar definition in the same
> header file. Maybe someone knows what
On Thu, 4 Apr 2013, Stephen Rothwell wrote:
> Date: Thu, 4 Apr 2013 10:43:19 +1100
> From: Stephen Rothwell
> To: Theodore Ts'o
> Cc: linux-n...@vger.kernel.org, linux-kernel@vger.kernel.org,
> Lukas Czerner
> Subject: linux-next: build failure after merge of the ext
failure after merge of the ext4 tree
Hi Ted,
After merging the ext4 tree, today's linux-next build (powerpc
ppc64_defconfig) failed like this:
fs/ext4/resize.c: In function 'ext4_resize_fs':
fs/ext4/ext4.h:1799:21: sorry, unimplemented: inlining failed in call to
'ext4_get_group_number
On Thu, Apr 04, 2013 at 03:18:32PM +0200, Lukáš Czerner wrote:
I am afraid I do not understand why this is happening. The commit
simply replaces ext4_get_group_no_and_offset() with
ext4_get_group_number() which has the similar definition in the same
header file. Maybe someone knows what this
failure after merge of the ext4 tree
On Thu, Apr 04, 2013 at 03:18:32PM +0200, Lukáš Czerner wrote:
I am afraid I do not understand why this is happening. The commit
simply replaces ext4_get_group_no_and_offset() with
ext4_get_group_number() which has the similar definition in the same
header
Hi Ted,
After merging the ext4 tree, today's linux-next build (powerpc
ppc64_defconfig) failed like this:
fs/ext4/resize.c: In function 'ext4_resize_fs':
fs/ext4/ext4.h:1799:21: sorry, unimplemented: inlining failed in call to
'ext4_get_group_number': function body not available
Hi Ted,
After merging the ext4 tree, today's linux-next build (powerpc
ppc64_defconfig) failed like this:
fs/ext4/resize.c: In function 'ext4_resize_fs':
fs/ext4/ext4.h:1799:21: sorry, unimplemented: inlining failed in call to
'ext4_get_group_number': function body not available
Sorry for the trouble. The following patch should fix the build.
From: Aditya Kali
Date: Mon, 9 Jul 2012 18:42:28 -0700
Subject: [PATCH] ext4: Fix compilation error for ext4_enable_quotas
ext4_enable_quotas should only be called under CONFIG_QUOTA
block.
Signed-off-by: Aditya Kali
---
Hi Ted,
After merging the ext4 tree, today's linux-next build (powerpc
ppc64_defconfig) failed like this:
fs/ext4/super.c: In function 'ext4_remount':
fs/ext4/super.c:4739:4: error: implicit declaration of function
'ext4_enable_quotas' [-Werror=implicit-function-declaration]
Caused by commit
Hi Ted,
After merging the ext4 tree, today's linux-next build (powerpc
ppc64_defconfig) failed like this:
fs/ext4/super.c: In function 'ext4_remount':
fs/ext4/super.c:4739:4: error: implicit declaration of function
'ext4_enable_quotas' [-Werror=implicit-function-declaration]
Caused by commit
Sorry for the trouble. The following patch should fix the build.
From: Aditya Kali adityak...@google.com
Date: Mon, 9 Jul 2012 18:42:28 -0700
Subject: [PATCH] ext4: Fix compilation error for ext4_enable_quotas
ext4_enable_quotas should only be called under CONFIG_QUOTA
block.
Signed-off-by:
66 matches
Mail list logo
