![]() | |||||||||||||
Messages in this thread |
On Wed, 14 May 2008 21:29:08 -0500 "Eric Van Hensbergen" <ericvh@gmail.com> wrote: > On Wed, May 14, 2008 at 7:05 PM, Andrew Morton > <akpm@linux-foundation.org> wrote: > > On Wed, 14 May 2008 19:00:12 -0500 > > "Eric Van Hensbergen" <ericvh@gmail.com> wrote: > > > > But I'm still reverting the v9fs tree due to > > > > git-v9fs is causing i386 allmodconfig failures: > > > > net/9p/trans_fd.o: In function `init_module': > > trans_fd.c:(.init.text+0x0): multiple definition of `init_module' > > net/9p/mod.o:mod.c:(.init.text+0x0): first defined here > > /opt/crosstool/gcc-4.1.0-glibc-2.3.6/i686-unknown-linux-gnu/bin/i686-unknown-linux-gnu-ld: Warning: size of symbol `init_module' changed from 27 in net/9p/mod.o to 128 in net/9p/trans_fd.o > > > > Okay, clearly I'm doing something wrong. I've tried the allmodconfig > on my local sandbox and its fine. When I look to see if there is > still a module_init in net/9p/trans_fd on kernel.org via gitweb, I > can't find it. (http://git.kernel.org/?p=linux/kernel/git/ericvh/v9fs.git;a=blob;f=net/9p/trans_fd.c;h=4507f744f44e527cc140b6b5601e556c10bfd361;hb=v9fs-devel) It has mysteriously gone away. Perhaps it was triggered by some other tree which was later fixed. > Are you pulling from my v9fs-devel tree or is --mm switched over to > pull from linux-next or something? The algorithm to determine this is to look at the first line of -mm's git-v9fs.patch: ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.26-rc2/2.6.26-rc2-mm1/broken-out/git-v9fs.patch has: GIT 38bfbd9f766f0b33de6bc16fd9ad1018b8fd3fe2 git+ssh://master.kernel.org/pub/scm/linux/kernel/git/ericvh/v9fs.git#v9fs-devel Yes, -mm uses both linux-next and git-v9fs (aka #v9fs-devel) linux-next uses #for-next and afacit that was empty as of a few hours ago. Nothing for 2.6.27? | ||||||||||||
| Last update: 2008-05-15 05:07 [from the cache] ©2003-2008 | |||||||||||||