From: Randy Dunlap <randy.dunlap@oracle.com>
To: linux-kernel@vger.kernel.org
Cc: Andrew Morton <akpm@linux-foundation.org>
Subject: Re: mmotm 2009-01-31-01-08 uploaded (staging vs. mach64: CONFIG_PANEL)
Date: Sat, 31 Jan 2009 11:53:36 -0800 [thread overview]
Message-ID: <4984AC40.8030708@oracle.com> (raw)
In-Reply-To: <200901310909.n0V99XIZ021497@imap1.linux-foundation.org>
akpm@linux-foundation.org wrote:
> The mm-of-the-moment snapshot 2009-01-31-01-08 has been uploaded to
>
> http://userweb.kernel.org/~akpm/mmotm/
>
> and will soon be available at
>
> git://git.zen-sources.org/zen/mmotm.git
drivers/staging/panel/Kconfig: config PANEL
vs. include/video/mach64.h: #define CONFIG_PANEL 0x00
When staging's CONFIG_PANEL=y (is enabled), the mach64.h header file gets
lots of these:
include/video/mach64.h:1257:1: warning: "CONFIG_PANEL" redefined
so staging adds a new config symbol that conflicts with the
(incorrect namespace) usage in mach64.h.
mach64 needs to change IMO, even though it is older.
--
~Randy
next parent reply other threads:[~2009-01-31 19:54 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200901310909.n0V99XIZ021497@imap1.linux-foundation.org>
2009-01-31 19:53 ` Randy Dunlap [this message]
2009-01-31 20:10 ` mmotm 2009-01-31-01-08 uploaded (staging vs. mach64: CONFIG_PANEL) Andrew Morton
2009-02-02 23:00 ` [PATCH 1/2] atyfb: fix CONFIG_ namespace violations Randy Dunlap
2009-02-03 8:09 ` [Linux-fbdev-devel] " Geert Uytterhoeven
2009-02-03 11:06 ` Ville Syrjälä
2009-02-03 22:23 ` Randy Dunlap
2009-02-03 23:58 ` Ville Syrjälä
2009-02-02 23:00 ` [PATCH 2/2] atyfb: fix header file trailing whitespace Randy Dunlap
2009-01-31 20:30 ` [PATCH -mmotm/fold] sysrq: emergency thaw only if CONFIG_BLOCK enabled Randy Dunlap
2009-01-31 20:32 ` [PATCH -mmotm/fold] UV: fix header struct usage Randy Dunlap
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=4984AC40.8030708@oracle.com \
--to=randy.dunlap@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.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