Mirror of the lttng-dev mailing list
 help / color / mirror / Atom feed
From: compudj@krystal.dyndns.org (Mathieu Desnoyers)
Subject: [ltt-dev] [PATCH] Don't use select
Date: Wed, 11 Feb 2009 02:21:12 -0500	[thread overview]
Message-ID: <20090211072112.GC10914@Krystal> (raw)
In-Reply-To: <20090211160830.7013.KOSAKI.MOTOHIRO@jp.fujitsu.com>

* KOSAKI Motohiro (kosaki.motohiro at jp.fujitsu.com) wrote:
> > * KOSAKI Motohiro (kosaki.motohiro at jp.fujitsu.com) wrote:
> > > Impact: Kconfig cleanup
> > > 
> > > many kernel developer hate select Kconfig syntax.
> > > it should be avoided.
> > > 
> > 
> > Hrm, about MARKERS, TRACEPOINT, DEBUG_FS, KPROBES, KALLSYMS,
> > FUNCTION_TRACER, the problem is that it can be frustrating for a user
> > who does not see the tracing options to figure out where to enable the
> > dependencies in the menus.
> > 
> > If we really want to remove the select, we'll have to find a more
> > suitable solution.
> 
> I can understand your point.
> but, "select" syntax discussion freqently repeated on LKML.
> at least, akpm strongly dislike it. (please google past discssion)
> 
> Then, I think "select" make hardly mainline merging.
> 
> 
> In other view, .config is edited _by_ developer, not end user.
> We can assume they can understand Kconfig file. Kconfig itself clearly
> described dependencies.
> 
> 
> However, if you have strongly opinion, I don't oppose it.
> Myself don't dislike "select", I merely want to merge lttng to mainline easily.
>

Another solution would be to bring together all the related options
(ftrace, debugfs, kprobes, lttng, ...) so they are clearly all available
in the same menu. What do you think ?

Mathieu


> 

-- 
Mathieu Desnoyers
OpenPGP key fingerprint: 8CD5 52C3 8E3C 4140 715F  BA06 3F25 A8FE 3BAE 9A68




  reply	other threads:[~2009-02-11  7:21 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-10  7:46 KOSAKI Motohiro
2009-02-11  5:02 ` Mathieu Desnoyers
2009-02-11  7:15   ` KOSAKI Motohiro
2009-02-11  7:21     ` Mathieu Desnoyers [this message]
2009-02-11  8:07       ` KOSAKI Motohiro

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=20090211072112.GC10914@Krystal \
    --to=compudj@krystal.dyndns.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