[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <ff9ba0cbc139d6f4937a892ceb5b6e9c@ozlabs.org>
Date: Wed, 10 Apr 2013 01:49:54 +1000
From: Stephen Rothwell <sfr@...b.auug.org.au>
To: Al Viro <viro@...iv.linux.org.uk>
Cc: <linux-next@...r.kernel.org>, <linux-kernel@...r.kernel.org>
Subject: Re: linux-next: build failure after merge of the vfs tree
Hi Al,
On 2013-04-08 11:15, Stephen Rothwell wrote:
>
> After merging the vfs tree, today's linux-next build (powerpc
> ppc64_defconfig) failed like this:
>
> arch/powerpc/kvm/../../../virt/kvm/kvm_main.c: In function
> 'kvm_init':
> arch/powerpc/kvm/../../../virt/kvm/kvm_main.c:2990:2: error:
> assignment of member 'owner' in read-only object
> arch/powerpc/kvm/../../../virt/kvm/kvm_main.c:2991:2: error:
> assignment of member 'owner' in read-only object
> arch/powerpc/kvm/../../../virt/kvm/kvm_main.c:2992:2: error:
> assignment of member 'owner' in read-only object
>
> Caused by commit d612df096dce ("constify a bunch of struct
> file_operations instances"). Grep is your friend ...
>
> I have used the vfs tree from next-230130405 for today.
Ping?
--
Cheers,
Stephen Rothwell
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists