From: Paul Mundt <lethal@linux-sh.org>
To: "Robert P. J. Day" <rpjday@crashcourse.ca>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: even *more* unused CONFIG variables at no extra charge
Date: Mon, 19 Nov 2007 22:43:16 +0900 [thread overview]
Message-ID: <20071119134316.GA12158@linux-sh.org> (raw)
In-Reply-To: <alpine.LFD.0.9999.0711160555530.13454@localhost.localdomain>
On Fri, Nov 16, 2007 at 06:15:48AM -0500, Robert P. J. Day wrote:
> ==== sh64 ====
> >>>>> DEVICE_MEMORY_START
> >>>>> FLASH_MEMORY_START
> >>>>> HDSP253_LED
> >>>>> PCI_BLOCK_START
> >>>>> PCIDEVICE_MEMORY_START
Yeah, these are mostly bogus and just never got removed. I'll poke
through it and kill them off or fix up the Makefiles to actually use
them (as in the HDSP253_LED case). Thanks for catching these, these sorts
of reports are really useful.
Have you considered tidying up your config checker and adding it as a
static analyser target with the existing set? 'make configcheck' or
something would be a reasonable addition.
next prev parent reply other threads:[~2007-11-19 13:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-16 11:15 even *more* unused CONFIG variables at no extra charge Robert P. J. Day
2007-11-19 13:43 ` Paul Mundt [this message]
2007-11-19 13:57 ` Robert P. J. Day
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=20071119134316.GA12158@linux-sh.org \
--to=lethal@linux-sh.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rpjday@crashcourse.ca \
/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