All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kumar Gala <galak@kernel.crashing.org>
To: u-boot@lists.denx.de
Subject: [U-Boot] [RFC] Centralise documentation of CONFIG_ options (and finding unused ones)
Date: Thu, 14 Apr 2011 04:14:22 -0500	[thread overview]
Message-ID: <FC3C7371-366D-47CE-A41F-A9C2E21BFF10@kernel.crashing.org> (raw)
In-Reply-To: <4DA2FDFB.1000901@gmail.com>

>> From this it is easy to find unused options (CONFIG_ARIA is found only as a
> #define in include/configs/aria.h for example)
> 
> So my RFC is twofold:
> 1) Should we start to systematically remove unused options
> 2) Should we centralise all options in a single README (or two, one for
> standard CONFIG options and one for CONFIG_SYS options)?

Can you post data for which options are not used.  While I think automatic removal is harsh, I think something close to automatic is reasonable.

- k

  parent reply	other threads:[~2011-04-14  9:14 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-11 13:11 [U-Boot] [RFC] Centralise documentation of CONFIG_ options (and finding unused ones) Graeme Russ
2011-04-14  6:17 ` Albert ARIBAUD
2011-04-14  8:36   ` Graeme Russ
2011-04-14  9:14 ` Kumar Gala [this message]
2011-04-16  7:16   ` Graeme Russ
2011-04-17 13:30     ` Timur Tabi
2011-04-17 19:26       ` Graeme Russ

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=FC3C7371-366D-47CE-A41F-A9C2E21BFF10@kernel.crashing.org \
    --to=galak@kernel.crashing.org \
    --cc=u-boot@lists.denx.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.