linux-kernel - Re: linux-next: Tree for June 2 (staging/comedi)

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]

Message-ID: <alpine.DEB.1.10.1006052043140.21893@vs81.sauer-cs.de>
Date:	Sat, 5 Jun 2010 20:50:57 +0400 (MSD)
From:	Alexander Kurz <linux@...la.de>
To:	Borislav Petkov <bp@...64.org>
cc:	Randy Dunlap <randy.dunlap@...cle.com>,
	Stephen Rothwell <sfr@...b.auug.org.au>,
	Alexander Kurz <linux@...babel.org>,
	linux-next@...r.kernel.org, LKML <linux-kernel@...r.kernel.org>,
	gregkh@...e.de
Subject: Re: linux-next: Tree for June 2 (staging/comedi)

Hi,
could you please repeat the test on 2.6.35-rc1-git3 or later

On Thu, 3 Jun 2010, Borislav Petkov wrote:
> I get a different set of errors with 2.6.35-rc1:
> 
> ERROR: "cfc_write_array_to_buffer" [drivers/staging/comedi/drivers/usbduxfast.ko] undefined!
> ERROR: "cfc_write_array_to_buffer" [drivers/staging/comedi/drivers/comedi_test.ko] undefined!
was caused by
> CONFIG_COMEDI_FC=y
and is fixed in 824196248c1f28aa7d151fd5b11d76182c751f19
by adding COMEDI_FC depends on COMEDI.
CONFIG_COMEDI_FC=m would be correct.

> ERROR: "subdev_8255_cleanup" [drivers/staging/comedi/drivers/das08.ko] undefined!
> ERROR: "subdev_8255_init" [drivers/staging/comedi/drivers/das08.ko] undefined! 
CONFIG_COMEDI_8255=m should have been set.
this should be as well fixed in 824196248c1f28aa7d151fd5b11d76182c751f19 
by pulling das08 out of the ISA group.

thanks, Alexander
--
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/