public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Keith Owens <kaos@ocs.com.au>
To: "Corisen" <csyap@starnet.gov.sg>
Cc: linux-kernel@vger.kernel.org
Subject: Re: warning during make modules
Date: Mon, 11 Dec 2000 23:06:18 +1100	[thread overview]
Message-ID: <1671.976536378@ocs3.ocs-net> (raw)
In-Reply-To: Your message of "Mon, 11 Dec 2000 19:05:42 +0800." <006901c06362$4e1333c0$050010ac@starnet.gov.sg>

On Mon, 11 Dec 2000 19:05:42 +0800, 
"Corisen" <csyap@starnet.gov.sg> wrote:
>Thanks for your reply. The below mentioned warning messages where displayed
>while using modutils 2.3.22. Guess I need to apply the patch you mentioned
>to removed all the anonying messages.
>
>As I've not applied any patch before, pls advise where should I download the
>patch and the instructions for patching pls.

The patch is in the original email, reproduced below.  It is against
linux-2.4.0-test12-pre7 but will fit -pre8 as well.  The Kernel-HOWTO
(part of the howto package) has a section on patching the kernel.

Index: 0-test12-pre7.1/include/linux/module.h
--- 0-test12-pre7.1/include/linux/module.h Thu, 07 Dec 2000 09:20:04 +1100 kaos (linux-2.4/W/33_module.h 1.1.2.1.2.1.2.1.2.1.1.3.1.1 644)
+++ 0-test12-pre7.2(w)/include/linux/module.h Mon, 11 Dec 2000 20:26:22 +1100 kaos (linux-2.4/W/33_module.h 1.1.2.1.2.1.2.1.2.1.1.3.1.2 644)
@@ -247,12 +247,6 @@ static const struct gtype##_id * __modul
   __attribute__ ((unused)) = name
 #define MODULE_DEVICE_TABLE(type,name)		\
   MODULE_GENERIC_TABLE(type##_device,name)
-/* not put to .modinfo section to avoid section type conflicts */
-
-/* The attributes of a section are set the first time the section is
-   seen; we want .modinfo to not be allocated.  */
-
-__asm__(".section .modinfo\n\t.previous");
 
 /* Define the module variable, and usage macros.  */
 extern struct module __this_module;

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

  reply	other threads:[~2000-12-11 12:37 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-11-19  1:11 Linux 2.2.18pre22 Alan Cox
2000-11-19  1:56 ` Miquel van Smoorenburg
2000-11-19  2:51 ` J . A . Magallon
2000-11-19  8:53 ` Jeff V. Merkey
2000-11-19 12:57   ` Alan Cox
2000-11-20  5:45     ` Jeff V. Merkey
2000-11-19 15:09   ` Kai Germaschewski
2000-11-20  5:50     ` Jeff V. Merkey
2000-11-20 10:10       ` Kai Germaschewski
2000-11-20 17:29         ` Jeff V. Merkey
2000-11-19 10:07 ` Michael Marxmeier
2000-12-11  9:15   ` warning during make modules Corisen
2000-12-11  9:27     ` Keith Owens
2000-12-11 11:05       ` Corisen
2000-12-11 12:06         ` Keith Owens [this message]
2000-11-20 11:33 ` Linux 2.2.18pre22 Arnaud S . Launay
2000-11-21  7:36 ` Tomasz K³oczko
2000-11-21  9:32   ` David S. Miller
2000-11-22 13:48 ` John Kennedy
  -- strict thread matches above, loose matches on Subject: below --
2000-12-11 23:42 warning during make modules Frédéric L . W . Meunier
2000-12-12  1:14 ` Keith Owens

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=1671.976536378@ocs3.ocs-net \
    --to=kaos@ocs.com.au \
    --cc=csyap@starnet.gov.sg \
    --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