From: Arnd Bergmann <arnd@arndb.de>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Jean Delvare <khali@linux-fr.org>, Hans Berglund <hb@spacetec.no>,
Jonas Bonn <jonas@southpole.se>,
linux-i2c@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] i2c: I2C_ELEKTOR should depend on HAS_IOPORT
Date: Tue, 16 Aug 2011 21:42:06 +0200 [thread overview]
Message-ID: <4991605.b7BYCfYE3S@wuerfel> (raw)
In-Reply-To: <CAMuHMdUk_xTwGbhG0MHkS-8rkF76b1fg193pPcs+9MVyB-qHQw@mail.gmail.com>
On Tuesday 16 August 2011 21:14:42 Geert Uytterhoeven wrote:
> >> config I2C_ELEKTOR
> >> tristate "Elektor ISA card"
> >> - depends on ISA && BROKEN_ON_SMP
> >> + depends on ISA && HAS_IOPORT && BROKEN_ON_SMP
> >> select I2C_ALGOPCF
> >> help
> >> This supports the PCF8584 ISA bus I2C adapter. Say Y if you own
> >
> > How can ISA be set if HAS_IOPORT is not? This shouldn't be allowed.
>
> It's always been like that. With CONFIG_ISA, we have inb() and friends. But not
> ioport_map(), which was introduced more recently.
Right. BTW, I'd really like to change that once I've picked up and fixed the
use of inb() in 8250.c. I think we should change CONFIG_HAS_IOPORT to mean
that inb(), ioport_resource and /proc/ioports are available, while a new
CONFIG_HAS_IOPORT_MAP can then replace the current CONFIG_HAS_IOPORT symbol.
Arnd
next prev parent reply other threads:[~2011-08-16 19:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-08 11:20 Geert Uytterhoeven
2011-08-16 17:50 ` Jean Delvare
2011-08-16 19:14 ` Geert Uytterhoeven
2011-08-16 19:42 ` Arnd Bergmann [this message]
2011-08-17 9:39 ` Jean Delvare
2011-08-29 7:48 ` Geert Uytterhoeven
2011-08-29 7:55 ` Jean Delvare
2011-08-29 8:13 ` Geert Uytterhoeven
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=4991605.b7BYCfYE3S@wuerfel \
--to=arnd@arndb.de \
--cc=geert@linux-m68k.org \
--cc=hb@spacetec.no \
--cc=jonas@southpole.se \
--cc=khali@linux-fr.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®