From: Arnd Bergmann <arnd@arndb•de>
To: linuxppc-dev@lists•ozlabs.org
Cc: Michael Ellerman <mpe@ellerman•id.au>,
linuxppc-dev@ozlabs•org, thuth@redhat•com
Subject: Re: [PATCH 1/6] powerpc/kconfig: Move NR_IRQS into "Kernel Options"
Date: Thu, 08 Oct 2015 23:30:27 +0200 [thread overview]
Message-ID: <7826129.RXlL8kStvO@wuerfel> (raw)
In-Reply-To: <1444338557-14988-1-git-send-email-mpe@ellerman.id.au>
On Friday 09 October 2015 08:09:12 Michael Ellerman wrote:
> Currently the NR_IRQS option sits at the top level, which is ugly in
> menuconfig. It's not something users will commonly need to worry about
> so move it into "Kernel Options".
>
> Signed-off-by: Michael Ellerman <mpe@ellerman•id.au>
>
Is this option actually still meaningful at all, when you select CONFIG_SPARSE_IRQ
unconditionally?
Arnd
next prev parent reply other threads:[~2015-10-08 21:30 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-08 21:09 [PATCH 1/6] powerpc/kconfig: Move NR_IRQS into "Kernel Options" Michael Ellerman
2015-10-08 21:09 ` [PATCH 2/6] powerpc/kconfig: Move sysdev Kconfig later Michael Ellerman
2015-10-09 5:54 ` Thomas Huth
2015-10-08 21:09 ` [PATCH 3/6] powerpc/kconfig: Move bitness & endian options to the top Michael Ellerman
2015-10-08 21:09 ` [PATCH 4/6] powerpc/kconfig: Move SCOM_DEBUGFS into "Kernel Hacking" Michael Ellerman
2015-10-08 21:09 ` [PATCH 5/6] powerpc/kconfig: Move cpu options after platform options Michael Ellerman
2015-10-09 5:47 ` Thomas Huth
2015-10-12 21:47 ` Scott Wood
2015-10-13 0:11 ` Michael Ellerman
2015-10-08 21:09 ` [PATCH 6/6] powerpc/kconfig: Cell CPU options should depend on PPC_CELL Michael Ellerman
2015-10-09 5:48 ` Thomas Huth
2015-10-08 21:30 ` Arnd Bergmann [this message]
2015-10-12 10:00 ` [PATCH 1/6] powerpc/kconfig: Move NR_IRQS into "Kernel Options" Michael Ellerman
2015-10-12 10:30 ` Arnd Bergmann
2015-10-12 11:07 ` Michael Ellerman
2015-10-12 11:50 ` Arnd Bergmann
2015-10-13 0:28 ` Michael Ellerman
2015-10-13 12:07 ` Arnd Bergmann
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=7826129.RXlL8kStvO@wuerfel \
--to=arnd@arndb$(echo .)de \
--cc=linuxppc-dev@lists$(echo .)ozlabs.org \
--cc=linuxppc-dev@ozlabs$(echo .)org \
--cc=mpe@ellerman$(echo .)id.au \
--cc=thuth@redhat$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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