linux-kernel - Re: debug Kconfig option (was Re: linux-next: Tree for April 9)

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20080410095112.GB12543@elte.hu>
Date:	Thu, 10 Apr 2008 11:51:12 +0200
From:	Ingo Molnar <mingo@...e.hu>
To:	Stefan Richter <stefanr@...6.in-berlin.de>
Cc:	linux-kernel@...r.kernel.org, linux-next@...r.kernel.org,
	Stephen Rothwell <sfr@...b.auug.org.au>
Subject: Re: debug Kconfig option (was Re: linux-next: Tree for April 9)


* Stefan Richter <stefanr@...6.in-berlin.de> wrote:

> > Commit 523a65f1a7a339e528ca6d6d808516fe195fde03 ("firewire: fw-ohci: 
> > add option for remote debugging") in the ieee1394 tree adds a new 
> > entry just where the sched tree adds
> > 
> > source kernel/trace/Kconfig
> 
> I grab this opportunity to ask the list: Would you prefer the remote 
> debugging option in the kernel hacking menu (as in the commit), or 
> rather in the respective driver submenu?

it's great stuff! I very much think it's fine in lib/Kconfig.debug - we 
need prominence of debugging options. (they are used way too 
infrequently)

My only suggestion would be to move the new entry below the existing 
firewire entry (PROVIDE_OHCI1394_DMA_INIT) there - which also happens to 
avoid this particular merge conflict.

	Ingo
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/