From: Christoph Hellwig <hch@infradead.org>
To: Arnd Bergmann <arnd@arndb.de>
Cc: Geert Uytterhoeven <geert@linux-m68k.org>,
Adrian Bunk <bunk@fs.tum.de>,
Christoph Hellwig <hch@infradead.org>,
wli@holomorphy.com, "David S. Miller" <davem@redhat.com>,
schwidefsky@de.ibm.com, linux390@de.ibm.com,
sparclinux@vger.kernel.org,
Linux/m68k <linux-m68k@lists.linux-m68k.org>,
Linux Kernel Development <linux-kernel@vger.kernel.org>
Subject: Re: architectures with their own "config PCMCIA"
Date: Wed, 11 Aug 2004 16:45:23 +0000 [thread overview]
Message-ID: <20040811174523.A30087@infradead.org> (raw)
In-Reply-To: <200408072341.17721.arnd@arndb.de>; from arnd@arndb.de on Sat, Aug 07, 2004 at 11:41:17PM +0200
On Sat, Aug 07, 2004 at 11:41:17PM +0200, Arnd Bergmann wrote:
> However, I just tried and found that out of the 23 driver submenus, only
> "Generic Driver Options", "Block devices", "SCSI device support",
> "Multi-device support", "Networking support" and "Character devices"
> make any sense at all. All others depend on some hardware that has
> never been attached to an s390 box.
>
> We could of course build some subsystems like MTD, ISDN or FB, but
> there is still little point without any low-level drivers.
That gives this type of code additional build coverage, which is a good
thing. Just allow it in the menues, no need to add it to your defconfigs :)
WARNING: multiple messages have this Message-ID (diff)
From: Christoph Hellwig <hch@infradead.org>
To: Arnd Bergmann <arnd@arndb.de>
Cc: Geert Uytterhoeven <geert@linux-m68k.org>,
Adrian Bunk <bunk@fs.tum.de>,
Christoph Hellwig <hch@infradead.org>,
wli@holomorphy.com, "David S. Miller" <davem@redhat.com>,
schwidefsky@de.ibm.com, linux390@de.ibm.com,
sparclinux@vger.kernel.org,
Linux/m68k <linux-m68k@lists.linux-m68k.org>,
Linux Kernel Development <linux-kernel@vger.kernel.org>
Subject: Re: architectures with their own "config PCMCIA"
Date: Wed, 11 Aug 2004 17:45:23 +0100 [thread overview]
Message-ID: <20040811174523.A30087@infradead.org> (raw)
In-Reply-To: <200408072341.17721.arnd@arndb.de>; from arnd@arndb.de on Sat, Aug 07, 2004 at 11:41:17PM +0200
On Sat, Aug 07, 2004 at 11:41:17PM +0200, Arnd Bergmann wrote:
> However, I just tried and found that out of the 23 driver submenus, only
> "Generic Driver Options", "Block devices", "SCSI device support",
> "Multi-device support", "Networking support" and "Character devices"
> make any sense at all. All others depend on some hardware that has
> never been attached to an s390 box.
>
> We could of course build some subsystems like MTD, ISDN or FB, but
> there is still little point without any low-level drivers.
That gives this type of code additional build coverage, which is a good
thing. Just allow it in the menues, no need to add it to your defconfigs :)
next prev parent reply other threads:[~2004-08-11 16:45 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-07 17:01 architectures with their own "config PCMCIA" Adrian Bunk
2004-08-07 17:01 ` Adrian Bunk
2004-08-07 17:10 ` Christoph Hellwig
2004-08-07 17:10 ` Christoph Hellwig
2004-08-07 17:25 ` Adrian Bunk
2004-08-07 17:25 ` Adrian Bunk
2004-08-07 18:12 ` Arnd Bergmann
2004-08-07 18:12 ` Arnd Bergmann
2004-08-07 20:36 ` Geert Uytterhoeven
2004-08-07 20:36 ` Geert Uytterhoeven
2004-08-07 21:41 ` Arnd Bergmann
2004-08-07 21:41 ` Arnd Bergmann
2004-08-11 16:45 ` Christoph Hellwig [this message]
2004-08-11 16:45 ` Christoph Hellwig
2004-08-11 20:17 ` Adrian Bunk
2004-08-11 20:17 ` Adrian Bunk
2004-08-11 21:40 ` Sam Ravnborg
2004-08-11 21:40 ` Sam Ravnborg
2004-08-12 0:10 ` Adrian Bunk
2004-08-12 0:10 ` Adrian Bunk
2004-08-12 8:59 ` Roman Zippel
2004-08-12 8:59 ` Roman Zippel
2004-08-14 20:47 ` Adrian Bunk
2004-08-14 20:47 ` Adrian Bunk
2004-08-15 17:32 ` Roman Zippel
2004-08-15 17:32 ` Roman Zippel
2004-08-15 19:37 ` Geert Uytterhoeven
2004-08-15 19:37 ` Geert Uytterhoeven
2004-08-15 20:15 ` Adrian Bunk
2004-08-15 20:15 ` Adrian Bunk
2004-08-15 23:01 ` Roman Zippel
2004-08-15 23:01 ` Roman Zippel
2004-08-15 23:22 ` Adrian Bunk
2004-08-15 23:22 ` Adrian Bunk
2004-08-11 21:45 ` Roman Zippel
2004-08-11 21:45 ` Roman Zippel
2004-08-12 0:18 ` Adrian Bunk
2004-08-12 0:18 ` Adrian Bunk
2004-08-12 2:19 ` Randy.Dunlap
2004-08-12 2:19 ` Randy.Dunlap
2004-08-11 16:54 ` William Lee Irwin III
2004-08-11 16:54 ` William Lee Irwin III
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=20040811174523.A30087@infradead.org \
--to=hch@infradead.org \
--cc=arnd@arndb.de \
--cc=bunk@fs.tum.de \
--cc=davem@redhat.com \
--cc=geert@linux-m68k.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-m68k@lists.linux-m68k.org \
--cc=linux390@de.ibm.com \
--cc=schwidefsky@de.ibm.com \
--cc=sparclinux@vger.kernel.org \
--cc=wli@holomorphy.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.