mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "J.A. Magallon" <jamagallon@able.es>
To: Roman Zippel <zippel@linux-m68k.org>
Cc: Lista Linux-Kernel <linux-kernel@vger.kernel.org>
Subject: Re: kbuild dependencies and layout
Date: Mon, 25 Oct 2004 23:32:25 +0000	[thread overview]
Message-ID: <1098747145l.19825l.0l@werewolf.able.es> (raw)
In-Reply-To: <Pine.LNX.4.61.0410251556430.17266@scrub.home> (from zippel@linux-m68k.org on Mon Oct 25 16:09:43 2004)


On 2004.10.25, Roman Zippel wrote:
> Hi,
> 
> On Sun, 24 Oct 2004, J.A. Magallon wrote:
> 
> > A_GENERIC_FEATURE_1 is valid for both submodels. Logic is right, but
> > gconfig insists on putting AF1 as a subentry of A_2, instead of hanging
> > it in the menu. I would like:
> > 
> >  A support
> >   \- A-1
> >   \- A-2
> >   \- AF1 (visible only when A-1 or A-2 are selected)
> >   \- AF2 (visible only when A-1 or A-2 are selected)
> 
> Could you please post a real example? There are two possibilities and it 
> depends on the context.

I'm trying to cleanup the config for Promise IDE, see

http://marc.theaimsgroup.com/?l=linux-kernel&m=109849081408193&w=2

Original code in drivers/ide/Kconfig for 2.6.9-mm1:

config BLK_DEV_PDC202XX_OLD
    tristate "PROMISE PDC202{46|62|65|67} support"
config PDC202XX_BURST
    bool "Special UDMA Feature"
    depends on BLK_DEV_PDC202XX_OLD
config BLK_DEV_PDC202XX_NEW
    tristate "PROMISE PDC202{68|69|70|71|75|76|77} support"
config PDC202XX_FORCE
    bool "Enable controller even if disabled by BIOS"
    depends on BLK_DEV_PDC202XX_NEW

(helps stripped...)
I want to make PDC202XX_BURST and PDC202XX_FORCE be selectable if any of
_OLD or _NEW is selected. So I wrote:

menu "Promise PDC support"
config BLK_DEV_PDC202XX_OLD
    tristate "PROMISE PDC202{46|62|65|67} support"
config BLK_DEV_PDC202XX_NEW 
    tristate "PROMISE PDC202{68|69|70|71|75|76|77} support"
config PDC202XX_BURST
    bool "Special UDMA Feature"
    depends on BLK_DEV_PDC202XX_OLD || BLK_DEV_PDC202XX_NEW
config PDC202XX_FORCE
    bool "Enable controller even if disabled by BIOS"
    depends on BLK_DEV_PDC202XX_OLD || BLK_DEV_PDC202XX_NEW
endmenu

Result (menuconfig) is:

  x x      <M> PROMISE PDC202{46|62|65|67} support                        x x  
  x x      < > PROMISE PDC202{68|69|70|71|75|76|77} support               x x  
  x x      [ ]   Special UDMA Feature (NEW)                               x x  
  x x      [ ]   Enable controller even if disabled by BIOS (NEW)         x x  

ie, the two flags are grouped inside the PDC_NEW config, instead of at
the same level.

I tried grouping things under submenus in several ways, with dummy config
variables, anyways it always ends up grouped below PDC_NEW, instead that at
the same level that both PDCs...

I have no idea on how to do it...

Any clue ?

TIA

--
J.A. Magallon <jamagallon()able!es>     \               Software is like sex:
werewolf!able!es                         \         It's better when it's free
Mandrakelinux release 10.1 (Community) for i586
Linux 2.6.9-jam1 (gcc 3.4.1 (Mandrakelinux 10.1 3.4.1-4mdk)) #1



  reply	other threads:[~2004-10-26  1:50 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-24 23:43 J.A. Magallon
2004-10-25 14:09 ` Roman Zippel
2004-10-25 23:32   ` J.A. Magallon [this message]
2004-10-27  0:19     ` Roman Zippel

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=1098747145l.19825l.0l@werewolf.able.es \
    --to=jamagallon@able.es \
    --cc=linux-kernel@vger.kernel.org \
    --cc=zippel@linux-m68k.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

all inboxes | Powered by JetHome®