linux-kernel - Re: linux-next: Tree for July 1 (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: <20110701154327.69c5b852.rdunlap@xenotime.net>
Date:	Fri, 1 Jul 2011 15:43:27 -0700
From:	Randy Dunlap <rdunlap@...otime.net>
To:	Stephen Rothwell <sfr@...b.auug.org.au>, gregkh <greg@...ah.com>,
	driverdevel <devel@...verdev.osuosl.org>
Cc:	linux-next@...r.kernel.org, LKML <linux-kernel@...r.kernel.org>,
	Ian Abbott <abbotti@....co.uk>,
	Frank Mori Hess <fmhess@...rs.sourceforge.net>
Subject: Re: linux-next: Tree for July 1 (staging/comedi)

On Fri, 1 Jul 2011 16:05:23 +1000 Stephen Rothwell wrote:

> Hi all,
> 
> Changes since 20110630:


drivers/staging/comedi/drivers/ni_labpc.c: In function 'labpc_common_attach':
drivers/staging/comedi/drivers/ni_labpc.c:602: error: implicit declaration of function 'request_dma'
drivers/staging/comedi/drivers/ni_labpc.c:608: error: implicit declaration of function 'claim_dma_lock'
drivers/staging/comedi/drivers/ni_labpc.c:611: error: implicit declaration of function 'release_dma_lock'
drivers/staging/comedi/drivers/ni_labpc.c: In function 'labpc_common_detach':
drivers/staging/comedi/drivers/ni_labpc.c:803: error: implicit declaration of function 'free_dma'


on x86_64 when CONFIG_ISA_DMA_API is not enabled.

Since that driver handles both ISA and PCI devices,
and the PCI parts are conditional, I guess that the ISA parts also
need to be made conditional.

---
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***
--
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/