From: Grant Coady <lkml@dodo.com.au>
To: Adrian Bunk <bunk@stusta.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.13-rc3 test: finding compile errors with make randconfig
Date: Mon, 25 Jul 2005 07:13:02 +1000 [thread overview]
Message-ID: <0fv7e11ejvimjkfqib95n93hl34icavnbu@4ax.com> (raw)
In-Reply-To: <20050724203932.GX3160@stusta.de>
On Sun, 24 Jul 2005 22:39:32 +0200, Adrian Bunk <bunk@stusta.de> wrote:
>On Mon, Jul 25, 2005 at 05:42:58AM +1000, Grant Coady wrote:
>> On Sun, 24 Jul 2005 11:13:27 +0200, Adrian Bunk <bunk@stusta.de> wrote:
>> >
>> >it's generally useful, but the target kernel should be the latest -mm
>> >kernel.
>> 097-error:drivers/char/drm/drm_memory.h:163: error: redefinition of `drm_ioremap_nocache'
>> 097-error:drivers/char/drm/drm_memory.h:163: error: `drm_ioremap_nocache' previously defined here
>> 097-error:drivers/char/drm/drm_memory.h:174: error: redefinition of `drm_ioremapfree'
>> 097-error:drivers/char/drm/drm_memory.h:174: error: `drm_ioremapfree' previously defined here
>
>This requires the .config for debugging.
Here:
ftp://ftp.scatter.mine.nu/develop/trial4-097-config.gz
>My first guess is that drm_memory.h requires a simple #ifdef to allow
>multiple inclusions.
I can tell you:
--- linux-2.6.12.3b/drivers/char/drm/drm_memory.h.orig 2005-06-18 05:48:29.000000000 +1000
+++ linux-2.6.12.3b/drivers/char/drm/drm_memory.h 2005-07-25 06:57:41.000000000 +1000
@@ -33,6 +33,9 @@
* OTHER DEALINGS IN THE SOFTWARE.
*/
+#ifndef DRM_MEMORY_H
+#define DRM_MEMORY_H
+
#include <linux/config.h>
#include <linux/highmem.h>
#include <linux/vmalloc.h>
@@ -194,4 +197,5 @@
iounmap(pt);
}
+#endif
does not fix it, though it's probably not what you had in mind, first try...
Simple fix didn't... Now I got to read the code, takes a little more
effort :)
...
>You aren't running into problems that are already fixed (see your second
>example above).
I see your point, thanks for feedback.
Grant.
next prev parent reply other threads:[~2005-07-24 21:13 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-24 6:28 Grant Coady
2005-07-24 9:13 ` Adrian Bunk
2005-07-24 19:42 ` Grant Coady
2005-07-24 20:14 ` Jesper Juhl
2005-07-24 20:39 ` Adrian Bunk
2005-07-24 21:13 ` Grant Coady [this message]
2005-07-24 21:27 ` Adrian Bunk
2005-07-24 21:49 ` Grant Coady
2005-07-26 1:26 ` Grant Coady
2005-07-26 9:55 ` Adrian Bunk
2005-07-24 13:01 ` Jesper Juhl
2005-07-24 19:23 ` Grant Coady
2005-07-24 19:30 ` Jesper Juhl
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=0fv7e11ejvimjkfqib95n93hl34icavnbu@4ax.com \
--to=lkml@dodo.com.au \
--cc=bunk@stusta.de \
--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
all inboxes | Powered by JetHome®