From: Roland Dreier <roland@topspin.com>
To: ultralinux@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: arch/sparc64/Kconfig
Date: Sat, 10 Jul 2004 04:05:45 +0000 [thread overview]
Message-ID: <52brio8q1y.fsf@topspin.com> (raw)
I recently tested building the OpenIB InfiniBand drivers for sparc64.
These drivers add a new drivers/infiniband directory and hook into the
kernel config system by adding a 'source "drivers/infiniband/Kconfig"'
to the drivers/Kconfig file.
However, I discovered that arch/sparc64/Kconfig includes individual
drivers/xxx/Kconfig files rather than the main drivers/Kconfig. This
means that hooking in the infiniband Kconfig requires changing the
sparc64 Kconfig.
I looked at arch/sparc64/Kconfig and found that the only files it does
not include that are included by drivers/Kconfig are
drivers/cdrom/Kconfig
drivers/char/Kconfig
drivers/macintosh/Kconfig
drivers/message/i2o/Kconfig
drivers/misc/Kconfig
cdrom is safe because the whole thing depends on ISA. macintosh is
safe because it depends on PPC || MAC. misc is safe because it only
includes one entry that depends on X86.
So I guess my questions are, first, is there any reason why the
message/i2o and especially the char Kconfigs are left out of the
sparc64 Kconfig, and second, would a patch changing sparc64 to use the
main drivers/Kconfig be accepted?
Thanks,
Roland
reply other threads:[~2004-07-10 4:05 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=52brio8q1y.fsf@topspin.com \
--to=roland@topspin.com \
--cc=linux-kernel@vger.kernel.org \
--cc=ultralinux@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