public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Eric S. Raymond" <esr@thyrsus.com>
To: David Woodhouse <dwmw2@infradead.org>
Cc: CML2 <linux-kernel@vger.kernel.org>, kbuild-devel@lists.sourceforge.net
Subject: Re: Dead symbol elimination, stage 1
Date: Thu, 19 Apr 2001 14:06:50 -0400	[thread overview]
Message-ID: <20010419140650.C3841@thyrsus.com> (raw)
In-Reply-To: <20010419131944.A3049@thyrsus.com> <16626.987702505@redhat.com>
In-Reply-To: <16626.987702505@redhat.com>; from dwmw2@infradead.org on Thu, Apr 19, 2001 at 06:48:25PM +0100

David Woodhouse <dwmw2@infradead.org>:
> 
> > -# CONFIG_MTD_SBC_MEDIAGX is not set
> > -# CONFIG_MTD_ELAN_104NC is not set
> > -# CONFIG_MTD_SA1100 is not set
> > -# CONFIG_MTD_DC21285 is not set
> > -# CONFIG_MTD_CSTM_CFI_JEDEC is not set
> >  # CONFIG_MTD_JEDEC is not set
> >  # CONFIG_MTD_MIXMEM is not set
> >  # CONFIG_MTD_OCTAGON is not set
> >  # CONFIG_MTD_VMAX is not set
> > -# CONFIG_MTD_NAND is not set
> > -# CONFIG_MTD_NAND_SPIA is not set
> 
> Please don't. People using some of these embedded architectures need to
> update to the latest MTD code (which includes those options) anyway, and I'm
> hoping to merge that all into 2.4 shortly.

Well, then, those symbols will stop being dead.  But note this: *none of
those MTD symbols are set*.  So the effect of losing these would not be
to lose any CML1 information, merely to make a few more questions visible
during make oldconfig.  This is a feature, not a bug.
 
> They're not doing any harm, are they?

They are helping create a dense thicket in which real bugs can hide.

The cross-referencer has already turned up several genuine errors, 
and will doubtless turn up more -- but if the reports are stuffed
full of meaningless crap about undead defconfig symbols that aren't 
even set, the genuine errors are going to be hard to notice.
-- 
		<a href="http://www.tuxedo.org/~esr/">Eric S. Raymond</a>

In every country and in every age, the priest has been hostile to
liberty. He is always in alliance with the despot, abetting his abuses
in return for protection to his own.
	-- Thomas Jefferson, 1814

  reply	other threads:[~2001-04-19 18:06 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-04-19 17:19 Dead symbol elimination, stage 1 Eric S. Raymond
2001-04-19 17:44 ` Russell King
2001-04-19 17:59   ` Eric S. Raymond
2001-04-19 19:36     ` rmk
2001-04-19 20:04     ` rmk
2001-04-19 21:15       ` David Woodhouse
2001-04-19 18:05   ` David Woodhouse
2001-04-19 18:14     ` Eric S. Raymond
2001-04-20  6:33       ` Eyal Lebedinsky
2001-04-19 17:48 ` David Woodhouse
2001-04-19 18:06   ` Eric S. Raymond [this message]
2001-04-19 21:06 ` [kbuild-devel] " Kai Germaschewski
2001-04-21 11:46   ` Armin Schindler

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=20010419140650.C3841@thyrsus.com \
    --to=esr@thyrsus.com \
    --cc=dwmw2@infradead.org \
    --cc=kbuild-devel@lists.sourceforge.net \
    --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