From: David Miller <davem@davemloft.net>
To: jcmvbkbc@gmail.com
Cc: balbi@ti.com, gregkh@linuxfoundation.org,
linux-arch@vger.kernel.org, fengguang.wu@intel.com,
kuninori.morimoto.gx@renesas.com, linux-usb@vger.kernel.org
Subject: Re: [balbi-usb:xceiv 3/3] drivers/usb/phy/rcar-phy.c:75:3: error: implicit declaration of function 'iowrite32'
Date: Thu, 01 Nov 2012 11:07:29 -0400 (EDT) [thread overview]
Message-ID: <20121101.110729.2080098706669174559.davem@davemloft.net> (raw)
In-Reply-To: <CAMo8BfLoU0GLpncX7YXy_VvveFnR6f6guPJTLNdtt3SWDK1fcg@mail.gmail.com>
From: Max Filippov <jcmvbkbc@gmail.com>
Date: Thu, 1 Nov 2012 16:47:14 +0300
> Strange, AFAICS architectures that use asm-generic/io.h (blackfin, openrisc,
> score, unicore32 and xtensa) also provide those functions.
They define HAVE_IOMEM, s390 does not, therefore you must protect
the driver Kconfig with HAVE_IOMEM.
next prev parent reply other threads:[~2012-11-01 15:07 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <50924f0a.QuF7xjrp4IUSKMwd%fengguang.wu@intel.com>
[not found] ` <20121101103339.GD410@arwen.pp.htv.fi>
[not found] ` <20121101105034.GE410@arwen.pp.htv.fi>
[not found] ` <20121101105034.GE410-S8G//mZuvNWo5Im9Ml3/Zg@public.gmane.org>
2012-11-01 13:04 ` [balbi-usb:xceiv 3/3] drivers/usb/phy/rcar-phy.c:75:3: error: implicit declaration of function 'iowrite32' Greg KH
2012-11-01 13:04 ` Greg KH
2012-11-01 13:23 ` Felipe Balbi
[not found] ` <20121101132342.GE12489-S8G//mZuvNWo5Im9Ml3/Zg@public.gmane.org>
2012-11-01 13:38 ` Bjørn Mork
2012-11-01 13:38 ` Bjørn Mork
2012-11-01 15:06 ` David Miller
2012-11-02 9:16 ` Felipe Balbi
[not found] ` <20121102091620.GE17938-S8G//mZuvNWo5Im9Ml3/Zg@public.gmane.org>
2012-11-02 10:05 ` Bjørn Mork
2012-11-02 10:05 ` Bjørn Mork
2012-11-01 13:47 ` Max Filippov
2012-11-01 14:29 ` Fengguang Wu
2012-11-01 15:07 ` David Miller [this message]
2012-11-02 9:17 ` Felipe Balbi
[not found] ` <20121101130420.GB20982-U8xfFu+wG4EAvxtiuMwx3w@public.gmane.org>
2012-11-01 15:53 ` James Bottomley
2012-11-01 15:53 ` James Bottomley
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=20121101.110729.2080098706669174559.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=balbi@ti.com \
--cc=fengguang.wu@intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=jcmvbkbc@gmail.com \
--cc=kuninori.morimoto.gx@renesas.com \
--cc=linux-arch@vger.kernel.org \
--cc=linux-usb@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