From: "Mike Frysinger" <vapier.adi@gmail.com>
To: "Robert P. J. Day" <rpjday@mindspring.com>
Cc: "Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>
Subject: Re: dead CONFIG variables in kernel Makefiles
Date: Fri, 6 Jul 2007 09:55:20 -0500 [thread overview]
Message-ID: <8bd0f97a0707060755q59a8fdc5j3c0d44e060eec9cf@mail.gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0707060553350.10501@localhost.localdomain>
On 7/6/07, Robert P. J. Day <rpjday@mindspring.com> wrote:
>
> in addition to references to non-existent CONFIG variables in header
> and source files, here's a list of such variables in Makefiles
> throughout the entire tree:
>
> ===== BF548 =====
> ./arch/blackfin/Makefile:cpu-$(CONFIG_BF548) := bf548
> ===== BF549 =====
> ./arch/blackfin/Makefile:cpu-$(CONFIG_BF549) := bf549
> ===== BF_REV_0_0 =====
> ./arch/blackfin/Makefile:rev-$(CONFIG_BF_REV_0_0) := 0.0
> ===== BF_REV_0_1 =====
> ./arch/blackfin/Makefile:rev-$(CONFIG_BF_REV_0_1) := 0.1
that's because we couldnt push the rest of the BF54x port until the
new merge window ... they'll be defined with 2.6.23
> ===== CPU_FREQ_BF533 =====
> ./arch/blackfin/mach-bf533/Makefile:obj-$(CONFIG_CPU_FREQ_BF533) += cpu.o
we changed names in the Kconfig but didnt sync that Makefile ... the
others got updated
-mike
next prev parent reply other threads:[~2007-07-06 14:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-06 9:55 Robert P. J. Day
2007-07-06 14:55 ` Mike Frysinger [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-03-26 23:32 Robert P. J. Day
2007-03-26 23:37 ` Roland Dreier
2007-03-26 23:49 ` David Miller
2007-03-27 0:34 ` Adrian Bunk
2007-03-27 23:53 ` Adrian Bunk
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=8bd0f97a0707060755q59a8fdc5j3c0d44e060eec9cf@mail.gmail.com \
--to=vapier.adi@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rpjday@mindspring.com \
/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
all inboxes | Powered by JetHome®