From: Timur Tabi <timur@freescale.com>
To: Simon Horman <horms@verge.net.au>
Cc: "Kumar Gala" <galak@kernel.crashing.org>,
sam@ravnborg.org, "Kim Phillips" <kim.phillips@freescale.com>,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
"Ismail Dönmez" <ismail@pardus.org.tr>,
"Michael Schmitz" <schmitz@debian.org>,
"Roman Zippel" <zippel@linux-m68k.org>,
"Geert Uytterhoeven" <geert@linux-m68k.org>,
"Johannes Berg" <johannes@sipsolutions.net>,
"Benjamin Herrenschmidt" <benh@kernel.crashing.org>,
"Paul Mackerras" <paulus@samba.org>
Subject: Re: Kconfig warnings on latest GIT
Date: Thu, 10 May 2007 21:32:24 -0500 [thread overview]
Message-ID: <4643D5B8.8050106@freescale.com> (raw)
In-Reply-To: <20070511022721.GI10715@verge.net.au>
Simon Horman wrote:
> I agree. I had thought a little about a kconfig fix. Though I'm
> wondering if removing the warning will lead to oodles of dangling
> symbols and invalid checks over time.
I'm pretty sure it will. Perhaps we need to have a lint for Kconfig?
next prev parent reply other threads:[~2007-05-11 2:33 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-07 21:04 Kconfig warnings on latest GIT Ismail Dönmez
2007-05-08 19:31 ` Kim Phillips
2007-05-08 20:11 ` Timur Tabi
2007-05-10 5:10 ` Simon Horman
2007-05-10 15:39 ` Johannes Berg
2007-05-11 1:22 ` Simon Horman
2007-05-11 11:45 ` Johannes Berg
2007-05-14 1:32 ` Simon Horman
2007-05-14 12:55 ` Johannes Berg
2007-05-14 14:24 ` Kumar Gala
2007-05-14 16:25 ` Johannes Berg
2007-05-23 12:37 ` Kumar Gala
2007-05-23 12:37 ` Kumar Gala
2007-05-23 13:57 ` Johannes Berg
2007-05-23 13:57 ` Johannes Berg
2007-05-23 14:14 ` Kumar Gala
2007-05-23 14:14 ` Kumar Gala
2007-05-23 14:26 ` Johannes Berg
2007-05-23 14:26 ` Johannes Berg
2007-05-10 16:56 ` Timur Tabi
2007-05-11 1:25 ` Simon Horman
2007-05-11 1:41 ` Kumar Gala
2007-05-11 1:47 ` Kumar Gala
2007-05-11 2:05 ` Simon Horman
2007-05-11 2:13 ` Kumar Gala
2007-05-11 2:27 ` Simon Horman
2007-05-11 2:32 ` Timur Tabi [this message]
2007-05-11 3:08 ` Simon Horman
2007-05-11 7:43 ` Russell King
2007-05-11 12:38 ` Timur Tabi
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=4643D5B8.8050106@freescale.com \
--to=timur@freescale.com \
--cc=benh@kernel.crashing.org \
--cc=galak@kernel.crashing.org \
--cc=geert@linux-m68k.org \
--cc=horms@verge.net.au \
--cc=ismail@pardus.org.tr \
--cc=johannes@sipsolutions.net \
--cc=kim.phillips@freescale.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=paulus@samba.org \
--cc=sam@ravnborg.org \
--cc=schmitz@debian.org \
--cc=zippel@linux-m68k.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 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.