From: Greg KH <greg@kroah.com>
To: Randy Dunlap <rdunlap@xenotime.net>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
driverdevel <devel@driverdev.osuosl.org>,
linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
Ian Abbott <abbotti@mev.co.uk>,
Frank Mori Hess <fmhess@users.sourceforge.net>
Subject: Re: linux-next: Tree for July 1 (staging/comedi)
Date: Fri, 1 Jul 2011 15:46:04 -0700 [thread overview]
Message-ID: <20110701224604.GA7469@kroah.com> (raw)
In-Reply-To: <20110701154327.69c5b852.rdunlap@xenotime.net>
On Fri, Jul 01, 2011 at 03:43:27PM -0700, Randy Dunlap wrote:
> 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.
Ick.
Care to make a patch?
thanks,
greg k-h
next prev parent reply other threads:[~2011-07-01 22:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-01 6:05 linux-next: Tree for July 1 Stephen Rothwell
2011-07-01 22:43 ` linux-next: Tree for July 1 (staging/comedi) Randy Dunlap
2011-07-01 22:46 ` Greg KH [this message]
2011-07-02 18:44 ` [PATCH -next] staging: fix comedi NI labpc driver build when ISA_DMA_API is not enabled Randy Dunlap
2011-07-02 21:07 ` Greg KH
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20110701224604.GA7469@kroah.com \
--to=greg@kroah.com \
--cc=abbotti@mev.co.uk \
--cc=devel@driverdev.osuosl.org \
--cc=fmhess@users.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=rdunlap@xenotime.net \
--cc=sfr@canb.auug.org.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).