mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Robert P. J. Day" <rpjday@crashcourse.ca>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: how about a massive reorg of the "Kernel hacking" submenu?
Date: Sat, 26 Jul 2008 09:18:54 -0400 (EDT)	[thread overview]
Message-ID: <alpine.LFD.1.10.0807260809140.3417@localhost.localdomain> (raw)


  this bit of whining is inspired by the observation that the "Kernel
hacking" submenu (at least under x86) has become ridiculously long and
seems only partially ordered by topic.  so some thoughts.

  first, rename it from "Kernel hacking" to "Kernel debugging" since,
well, pretty much *everything* you can do with "make *config" can be
considered "hacking" so that submenu title isn't particularly
informative.  and once that's done, really make it related to
exclusively debugging selections, which has some implications.

  first, debugging content from elsewhere should be shifted under
here, such as "kprobes" and "markers" which currently reside under
"General setup," which seems a bit odd.  and perhaps all
profiling-related selections could be moved here as well.  (BTW, is
"Profiling support" really still EXPERIMENTAL?  just curious.)

  at the same time, some stuff could be moved *out* from under "Kernel
hacking," such as "Sample kernel code."  right now, it's buried
partway down the hacking selection list, but i think it's useful
enough to deserve its own top-level entry at the bottom of the menu.
and if it's more prominent, that would encourage more people to write
code samples, as opposed to having that selection buried in the
Hacking/Debugging submenu where people might not even see it.  (and
being able to build sample kernel code really has nothing to do with
debugging, anyway.)

  anyway, just some random thoughts from an early saturday morning
at OLS 2008, waiting for someone to show up and turn on the
$^$(*&^#)*^_# wireless.

rday

p.s.  it should go without saying that it would be nice for a newer
"Kernel debugging" submenu to collect related topics into subsubmenus
to shorten what's there, like perhaps having a single selection to
debug all mutex/spinlock-related stuff, that sort of thing.  the
current layout *desperately* needs some subsubmenus for readability.
or at least a few comments to break things up.

--

========================================================================
Robert P. J. Day
Linux Consulting, Training and Annoying Kernel Pedantry:
    Have classroom, will lecture.

http://crashcourse.ca                          Waterloo, Ontario, CANADA
========================================================================

                 reply	other threads:[~2008-07-26 13:20 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=alpine.LFD.1.10.0807260809140.3417@localhost.localdomain \
    --to=rpjday@crashcourse.ca \
    --cc=linux-kernel@vger.kernel.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®