From: Eyal Lebedinsky <eyal@eyal.emu.id.au>
To: unlisted-recipients:; (no To-header on input)@localhost.localdomain
Cc: esr@thyrsus.com, CML2 <linux-kernel@vger.kernel.org>
Subject: Re: Dead symbol elimination, stage 1
Date: Fri, 20 Apr 2001 16:33:08 +1000 [thread overview]
Message-ID: <3ADFD824.C666FAA5@eyal.emu.id.au> (raw)
In-Reply-To: <20010419135955.A3841@thyrsus.com> <20010419131944.A3049@thyrsus.com> <20010419184444.A3111@flint.arm.linux.org.uk> <20010419135955.A3841@thyrsus.com> <18282.987703518@redhat.com> <20010419141425.A4461@thyrsus.com>
"Eric S. Raymond" wrote:
>
> David Woodhouse <dwmw2@infradead.org>:
> >
> > esr@thyrsus.com said:
> > > I read this as "I haven't fixed the problem because..." not as
> > > "Don't fix the problem." Please be more explicit next time so I won't
> > > step on your toes?
> >
> > "This is not a problem, please don't \"fix\" it".
>
> But it is. The more false positives I get in the dead-symbol reports,
> the harder it will be to spot real problems like that business in the
> ARM kernel.c file.
Eric,
I found myself in similar situations in the past, and my solution was
to establish a small file of "do not report" symbols. I then use this
file to avoid reporting problems with items that I know are being
handled or are known false positives. Yes, it is not automagic, but
it does do the job.
The file might also include private notes as to the status of each
excluded symbol.
--
Eyal Lebedinsky (eyal@eyal.emu.id.au) <http://samba.anu.edu.au/eyal/>
next prev parent reply other threads:[~2001-04-20 6:34 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 [this message]
2001-04-19 17:48 ` David Woodhouse
2001-04-19 18:06 ` Eric S. Raymond
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=3ADFD824.C666FAA5@eyal.emu.id.au \
--to=eyal@eyal.emu.id.au \
--cc=esr@thyrsus.com \
--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