[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20180802135421.GA13512@infradead.org>
Date: Thu, 2 Aug 2018 06:54:21 -0700
From: Christoph Hellwig <hch@...radead.org>
To: Alexei Colin <acolin@....edu>
Cc: Geert Uytterhoeven <geert@...ux-m68k.org>, alex.bou9@...il.com,
Christoph Hellwig <hch@...radead.org>,
Linux MIPS Mailing List <linux-mips@...ux-mips.org>,
Catalin Marinas <catalin.marinas@....com>,
the arch/x86 maintainers <x86@...nel.org>,
Will Deacon <will.deacon@....com>,
Russell King <linux@...linux.org.uk>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
jwalters@....edu, Andrew Morton <akpm@...ux-foundation.org>,
linuxppc-dev <linuxppc-dev@...ts.ozlabs.org>,
Linux ARM <linux-arm-kernel@...ts.infradead.org>
Subject: Re: [RESEND PATCH 6/6] arm64: enable RapidIO menu in Kconfig
On Thu, Aug 02, 2018 at 09:45:44AM -0400, Alexei Colin wrote:
> If I move RapidIO option to drivers/Kconfig, then it won't appear under
> the Bus Options/System Support menu, along with other choices for the
> system bus (PCI, PCMCIA, ISA, TC, ...).
It's not like anyone cares. And FYI, moving all those to
drivers/Kconfig is osmething I will submit for the next merge window.
> Alex explains above that RapidIO
> may be selected as a system bus on some architectures, and users expect
> it to be in the menu in which it has been for some time now. What
> problem is the current organization causing?
A "system bus" seems like a rather outdated concept to start with.
Powered by blists - more mailing lists