From: Paul Mundt <lethal@linux-sh.org>
To: "Robert P. J. Day" <rpjday@crashcourse.ca>
Cc: magnus.damm@gmail.com,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: bad CONFIG variable references from Makefiles
Date: Tue, 29 Jul 2008 08:31:19 +0900 [thread overview]
Message-ID: <20080728233119.GC28055@linux-sh.org> (raw)
In-Reply-To: <alpine.LFD.1.10.0807281923310.31937@localhost.localdomain>
On Mon, Jul 28, 2008 at 07:24:47PM -0400, Robert P. J. Day wrote:
> On Tue, 29 Jul 2008, Paul Mundt wrote:
>
> > On Mon, Jul 28, 2008 at 04:09:28PM -0400, Robert P. J. Day wrote:
> > >
> > > a complete list of all references to non-existent CONFIG variables
> > > exclusively from Makefiles in the tree. since the list is so short,
> > > i'm not bothering to break it up by subsystem or arch. enjoy.
> > >
> > >
> > > ===== FB_SH7343VOU =====
> > > ./drivers/video/Makefile:obj-$(CONFIG_FB_SH7343VOU) += sh7343_voufb.o
> >
> > Seems to have crept in from a working local tree. It's obviously
> > bogus and can simply be killed off.
>
> ok, i can slap together a patch unless someone else gets to it first.
>
Already in my tree, forgot to mention :-)
next prev parent reply other threads:[~2008-07-28 23:32 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-28 20:09 bad CONFIG variable references from Makefiles Robert P. J. Day
2008-07-28 20:54 ` Paul Mundt
2008-07-28 23:24 ` Robert P. J. Day
2008-07-28 23:31 ` Paul Mundt [this message]
2008-07-28 23:32 ` Robert P. J. Day
2008-07-28 21:48 ` Adrian Bunk
2008-08-04 13:24 ` Mauro Carvalho Chehab
2008-08-05 18:00 ` [2.6 patch] remove the dead CONFIG_RADIO_MIROPCM20{,_RDS} code Adrian Bunk
2008-07-28 21:57 ` bad CONFIG variable references from Makefiles Adrian Bunk
2008-07-28 22:10 ` Russell King
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=20080728233119.GC28055@linux-sh.org \
--to=lethal@linux-sh.org \
--cc=linux-kernel@vger.kernel.org \
--cc=magnus.damm@gmail.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.