From: Grant Likely <grant.likely@secretlab.ca>
To: Michal Marek <mmarek@suse.cz>, Paul Thompson <set.mailinglist@gmail.com>
Cc: linux-kbuild@vger.kernel.org, linux-kernel@vger.kernel.org,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: IRQ subsystem menu
Date: Thu, 29 Nov 2012 20:32:42 +0000 [thread overview]
Message-ID: <20121129203242.6D6CD3E09C2@localhost> (raw)
In-Reply-To: <20121029140308.GA19316@sepie.suse.cz>
On Mon, 29 Oct 2012 15:03:08 +0100, Michal Marek <mmarek@suse.cz> wrote:
> (Adding lkml and Thomas as IRQ subsystem maintainer to CC)
>
> On Sun, Oct 21, 2012 at 03:40:16AM -0400, Paul Thompson wrote:
> > Hi;
> >
> > In menuconfig, General setup -> IRQ subsystem, there are two
> > possible menu-items. One depends partly on IRQ_DOMAIN, and the other
> > on MAY_HAVE_SPARSE_IRQ.
> >
> > On the x86-64 arch, neither of these seems to be set, so the
> > menu entry is blank if entered (displaying an odd ^@ if you try to
> > navigate up or down. And sometimes some screen garbage on the sides.)
> >
> > Previously (in the 3.2 kernel at least) this menu used to be
> > populated by the "Support sparse IRQ numbering" menu-item, which
> > at that time depended on HAVE_SPARSE_IRQ, and was forced to YES.
> >
> > I do not know if the current behaviour is intended, but it
> > is ugly and confusing to be confronted with a blank menu page.
> >
> > Ideally, the "IRQ subsystem" menu would not even show up
> > if it would contain no menu-items, but I do not know enough to
> > formulate that constraint.
First, move the 'menu "IRQ subsystem"' line does to right before the
IRQ_DOMAIN_DEBUG line so that it wraps the options that matter, then you
can add a "depends on MAY_HAVE_SPARSE_IRQ || IRQ_DOMAIN" line right
below the menu item.
You'll also need to move the IRQ_FORCED_THREADING line out from inside
the menu block.
Try it out and let me know how it goes.
g.
next prev parent reply other threads:[~2012-11-29 22:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-21 7:40 IRQ subsystem menu Paul Thompson
2012-10-29 14:03 ` Michal Marek
2012-11-29 20:32 ` Grant Likely [this message]
2012-12-06 2:16 ` Paul Thompson
2012-12-10 23:18 ` Grant Likely
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=20121129203242.6D6CD3E09C2@localhost \
--to=grant.likely@secretlab.ca \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mmarek@suse.cz \
--cc=set.mailinglist@gmail.com \
--cc=tglx@linutronix.de \
/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.