From: Fengguang Wu <fengguang.wu@intel.com>
To: linux-s390@vger.kernel.org
Subject: Re: sound/pci/lx6464es/lx6464es.c:557:2: error: implicit declaration of function 'ioport_unmap'
Date: Tue, 02 Apr 2013 13:02:53 +0000 [thread overview]
Message-ID: <20130402130253.GA9127@localhost> (raw)
In-Reply-To: <20130402103101.GA4118@osiris>
On Tue, Apr 02, 2013 at 12:31:01PM +0200, Heiko Carstens wrote:
> On Tue, Apr 02, 2013 at 10:35:21AM +0200, Takashi Iwai wrote:
> > At Fri, 29 Mar 2013 12:29:11 +0100,
> > Tim Blechmann wrote:
> > >
> > > hi,
> > > > sound/pci/lx6464es/lx6464es.c:556:2: error: implicit declaration of function 'iounmap' [-Werror=implicit-function-declaration]
> > > i'm not really familiar with the s390 architecture. are the specific
> > > functions declared in a different header or are they not available at
> > > all? in the second case, i'd suggest to disable this driver on this
> > > architecture, as it seems highly unlikely that anyone is going to use
> > > this hardware on this architecture (it would not surprise me, if i'm the
> > > only user of this hardware on linux)
> >
> > Heiko's patch added already the dependency on CONFIG_HAS_IOPORT in
> > sound/pci/Kconfig (commit 262d62eb), and I thought this should have
> > fixed the issue.
> >
> > Heiko, could you check it again?
>
> Yes, all is fine. It seems to be a bug in Fengguang's bisect script that
> caused a couple of false positives.
Yeah, sorry for the noise! I cannot reproduce the problem, either.
Thanks,
Fengguang
next parent reply other threads:[~2013-04-02 13:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20130402103101.GA4118@osiris>
2013-04-02 13:02 ` Fengguang Wu [this message]
[not found] <20130329015630.GA9085@localhost>
2013-03-29 11:29 ` sound/pci/lx6464es/lx6464es.c:557:2: error: implicit declaration of function 'ioport_unmap' Tim Blechmann
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=20130402130253.GA9127@localhost \
--to=fengguang.wu@intel.com \
--cc=linux-s390@vger.kernel.org \
/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