The Linux Kernel Mailing List
 help / color / mirror / Atom feed
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: Tests of undefined CONFIG variables.
Date: Wed, 13 Feb 2008 20:30:03 +0900	[thread overview]
Message-ID: <20080213113003.GA17418@linux-sh.org> (raw)
In-Reply-To: <alpine.LFD.1.00.0802130552370.19968@localhost.localdomain>

On Wed, Feb 13, 2008 at 05:54:12AM -0500, Robert P. J. Day wrote:
>   i've also updated the list of what i call "badref" CONFIG variables
> -- that is, tests of CONFIG_ variables that appear to be undefined
> anywhere in a Kconfig file (which typically represents a meaningless
> test, naturally).
> 
> http://www.crashcourse.ca/wiki/index.php/Badref_CONFIG_variables
> 
For SH:

CONFIG_SERIAL
CONFIG_CPU_HAS_PINT_IRQ
CONFIG_LITTLE_ENDIAN
CONFIG_SH64_PROC_TLB

are now fixed, thanks.

  reply	other threads:[~2008-02-13 11:31 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-13 10:54 Tests of undefined CONFIG variables Robert P. J. Day
2008-02-13 11:30 ` Paul Mundt [this message]
2008-02-13 11:35   ` Robert P. J. Day
2008-02-13 13:34 ` Haavard Skinnemoen

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=20080213113003.GA17418@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