LinuxPPC-Dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Marcelo Dalmas <m_dalmas@yahoo.com.br>
To: linuxppc-dev@ozlabs.org
Subject: [PATCH] Fix for disabling BUG
Date: Thu, 17 Apr 2008 12:33:33 -0700 (PDT)	[thread overview]
Message-ID: <85905.92547.qm@web50306.mail.re2.yahoo.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 286 bytes --]

Hi,

With CONFIG_BUG option disabled module_find_bug fuction (module_32.c and module_64.c) don't compile because struct bug_entry isn't defined.


Marcelo Dalmas


      Abra sua conta no Yahoo! Mail, o único sem limite de espaço para armazenamento!
http://br.mail.yahoo.com/

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: powerpc-config-bug.patch --]
[-- Type: text/x-diff; name="powerpc-config-bug.patch", Size: 858 bytes --]

Index: arch/powerpc/kernel/module_64.c
===================================================================
--- arch/powerpc/kernel/module_64.c	(revisão 51)
+++ arch/powerpc/kernel/module_64.c	(cópia de trabalho)
@@ -467,6 +467,7 @@
 	module_bug_cleanup(mod);
 }
 
+#ifdef CONFIG_BUG
 struct bug_entry *module_find_bug(unsigned long bugaddr)
 {
 	struct mod_arch_specific *mod;
@@ -481,3 +482,4 @@
 	}
 	return NULL;
 }
+#endif
Index: arch/powerpc/kernel/module_32.c
===================================================================
--- arch/powerpc/kernel/module_32.c	(revisão 51)
+++ arch/powerpc/kernel/module_32.c	(cópia de trabalho)
@@ -317,6 +317,7 @@
 	module_bug_cleanup(mod);
 }
 
+#ifdef CONFIG_BUG
 struct bug_entry *module_find_bug(unsigned long bugaddr)
 {
 	struct mod_arch_specific *mod;
@@ -331,3 +332,4 @@
 	}
 	return NULL;
 }
+#endif

                 reply	other threads:[~2008-04-17 19:40 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=85905.92547.qm@web50306.mail.re2.yahoo.com \
    --to=m_dalmas@yahoo.com.br \
    --cc=linuxppc-dev@ozlabs.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