Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Ralf Baechle <ralf@linux-mips.org>
To: "Kevin D. Kissell" <kevink@mips.com>
Cc: linux-mips@linux-mips.org
Subject: Re: dead(?) MIPS config stuff
Date: Thu, 5 Jul 2007 17:36:59 +0100	[thread overview]
Message-ID: <20070705163658.GA22652@linux-mips.org> (raw)
In-Reply-To: <01dc01c7bf20$e03f6c20$10eca8c0@grendel>

On Thu, Jul 05, 2007 at 06:23:45PM +0200, Kevin D. Kissell wrote:

> It's cruft, but it's cruft that does have some utility when porting SMTC to a new
> platform, as it helps identify interrupt management bugs.  It needs to be eliminated
> or replaced with a revision of the interface between architecture and platform 
> support for SMTC, toward which I've made some small progress recently, 
> but I'd prefer not to see it disappear before reinforcements arrive.

All this email was about were kernel configuration options that can't be
enabled for some reason.  Of course these automated checkers such as
Robert's make the assumption that the CONFIG_* preprocessor namespace
is rserved for the Kconfig system.  In this particular case the reason
is quite simple:

> arch/mips/kernel/process.c:54:#ifdef CONFIG_SMTC_IDLE_HOOK_DEBUG
> arch/mips/Kconfig.debug:40:config CONFIG_SMTC_IDLE_HOOK_DEBUG

The kconfig system itself does prefix names with CONFIG_ so kconfig
ends up defining CONFIG_CONFIG_SMTC_IDLE_HOOK_DEBUG (are we stuttuttering?)
So this one is fixed trivially.

  Ralf

  parent reply	other threads:[~2007-07-05 16:37 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-05 14:46 dead(?) MIPS config stuff Ralf Baechle
2007-07-05 15:01 ` Robert P. J. Day
2007-07-05 15:26   ` Ralf Baechle
2007-07-05 15:26     ` Robert P. J. Day
2007-07-05 15:27 ` Maciej W. Rozycki
2007-07-05 16:03 ` Sergei Shtylyov
2007-07-12 16:56   ` Atsushi Nemoto
2007-07-05 16:23 ` Kevin D. Kissell
2007-07-05 16:23   ` Kevin D. Kissell
2007-07-05 16:28   ` Robert P. J. Day
2007-07-05 16:37     ` Ralf Baechle
2007-07-05 16:48       ` Geert Uytterhoeven
2007-07-05 16:36   ` Ralf Baechle [this message]
2007-07-05 16:45     ` Ralf Baechle

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=20070705163658.GA22652@linux-mips.org \
    --to=ralf@linux-mips.org \
    --cc=kevink@mips.com \
    --cc=linux-mips@linux-mips.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