From: Richard Weinberger <richard@nod.at>
To: linux-kernel@vger.kernel.org
Cc: user-mode-linux-devel@lists.sourceforge.net,
viro@zeniv.linux.org.uk, Artem.Bityutskiy@linux.intel.com,
linux-mtd@lists.infradead.org,
Richard Weinberger <richard@nod.at>
Subject: [PATCH 1/5] Introduce CONFIG_GENERIC_IO
Date: Tue, 7 Feb 2012 01:22:46 +0100 [thread overview]
Message-ID: <1328574170-2286-1-git-send-email-richard@nod.at> (raw)
There are situations where CONFIG_HAS_IOMEM is too restrictive.
For example CONFIG_MTD_NAND_NANDSIM depends on CONFIG_HAS_IOMEM
but it works perfectly fine if an architecture without io memory
just includes asm-generic/io.h or implements everything defined in it.
UML is such a corner case.
Signed-off-by: Richard Weinberger <richard@nod.at>
---
lib/Kconfig | 5 +++++
1 files changed, 5 insertions(+), 0 deletions(-)
diff --git a/lib/Kconfig b/lib/Kconfig
index d69d321..c3c4c1c 100644
--- a/lib/Kconfig
+++ b/lib/Kconfig
@@ -26,6 +26,10 @@ config GENERIC_IOMAP
bool
select GENERIC_PCI_IOMAP
+config GENERIC_IO
+ boolean
+ default n
+
config CRC_CCITT
tristate "CRC-CCITT functions"
help
@@ -221,6 +225,7 @@ config BTREE
config HAS_IOMEM
boolean
depends on !NO_IOMEM
+ select GENERIC_IO
default y
config HAS_IOPORT
--
1.7.6
next reply other threads:[~2012-02-07 0:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-07 0:22 Richard Weinberger [this message]
2012-02-07 0:22 ` [uml-devel] [PATCH 2/5] um: Serve io_remap_pfn_range() Richard Weinberger
2012-02-07 0:22 ` [uml-devel] [PATCH 3/5] um: a bunch of headers can be killed by using generic-y Richard Weinberger
2012-02-07 0:22 ` [uml-devel] [PATCH 4/5] um: Wire CONFIG_GENERIC_IO up Richard Weinberger
2012-02-07 0:22 ` [uml-devel] [PATCH 5/5] MTD: Relax dependencies Richard Weinberger
2012-02-07 11:58 ` Artem Bityutskiy
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=1328574170-2286-1-git-send-email-richard@nod.at \
--to=richard@nod.at \
--cc=Artem.Bityutskiy@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=user-mode-linux-devel@lists.sourceforge.net \
--cc=viro@zeniv.linux.org.uk \
/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