linux-kernel - Re: build #355 issue for v2.6.25-rc2-15-g1309d4e in function v4l2_i2c

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Mon, 18 Feb 2008 17:36:02 +0100
From:	"Rafael J. Wysocki" <rjw@...k.pl>
To:	Mauro Carvalho Chehab <mchehab@...radead.org>
Cc:	Toralf Förster <toralf.foerster@....de>,
	video4linux-list@...hat.com, linux-kernel@...r.kernel.org
Subject: Re: build #355 issue for v2.6.25-rc2-15-g1309d4e in function v4l2_i2c_attach

On Monday, 18 of February 2008, Mauro Carvalho Chehab wrote:
> On Sun, 17 Feb 2008 11:21:09 +0100
> Toralf Förster <toralf.foerster@....de> wrote:
> 
> > Hello,
> > 
> > the build with the attached .config failed, make ends with:
> > ...
> >   CC      arch/x86/lib/usercopy_32.o
> >   AR      arch/x86/lib/lib.a
> >   LD      vmlinux.o
> >   MODPOST vmlinux.o
> > WARNING: modpost: Found 1 section mismatch(es).
> > To see full details build your kernel with:
> > 'make CONFIG_DEBUG_SECTION_MISMATCH=y'
> >   GEN     .version
> >   CHK     include/linux/compile.h
> >   UPD     include/linux/compile.h
> >   CC      init/version.o
> >   LD      init/built-in.o
> >   LD      .tmp_vmlinux1
> > drivers/built-in.o: In function `v4l2_i2c_attach':
> > (.text+0x26c67): undefined reference to `i2c_attach_client'
> > make: *** [.tmp_vmlinux1] Error 1
> 
> This bug were already fixed. I'm waiting for Linus to pull. The patches fixing
> it are available at:
> 
> http://git.kernel.org/?p=linux/kernel/git/mchehab/v4l-dvb.git

Specific commits or just everything?

Rafael
--
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/