From: Ingo Molnar <mingo@elte.hu>
To: Kamalesh Babulal <kamalesh@linux.vnet.ibm.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
ptiedem@de.ibm.com, braunu@de.ibm.com, jeff@garzik.org,
linux-s390@vger.kernel.org, Andy Whitcroft <apw@shadowen.org>,
Balbir Singh <balbir@linux.vnet.ibm.com>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [build failure] Re: Linux 2.6.24-rc4 on S390x
Date: Tue, 4 Dec 2007 11:32:38 +0100 [thread overview]
Message-ID: <20071204103237.GA15038@elte.hu> (raw)
In-Reply-To: <47552A98.9010108@linux.vnet.ibm.com>
* Kamalesh Babulal <kamalesh@linux.vnet.ibm.com> wrote:
> The patch ctc: make use of alloc_netdev() (commit
> 1c1478859017452a1179dbbdf7b9eb5b48438746) introduces the build failure
>
> CC [M] drivers/s390/net/fsm.o
> CC [M] drivers/s390/net/smsgiucv.o
> CC [M] drivers/s390/net/ctcmain.o
> drivers/s390/net/ctcmain.c: In function `ctc_init_netdevice':
> drivers/s390/net/ctcmain.c:2805: error: implicit declaration of function `SET_MODULE_OWNER'
> make[2]: *** [drivers/s390/net/ctcmain.o] Error 1
> make[1]: *** [drivers/s390/net] Error 2
> make: *** [drivers/s390] Error 2
the patch below should fix this.
Ingo
------------>
Subject: drivers/s390/net/ctcmain.c: fix build bug
From: Ingo Molnar <mingo@elte.hu>
SET_MODULE_OWNER() is obsolete.
Signed-off-by: Ingo Molnar <mingo@elte.hu>
---
drivers/s390/net/ctcmain.c | 1 -
1 file changed, 1 deletion(-)
Index: linux/drivers/s390/net/ctcmain.c
===================================================================
--- linux.orig/drivers/s390/net/ctcmain.c
+++ linux/drivers/s390/net/ctcmain.c
@@ -2802,7 +2802,6 @@ void ctc_init_netdevice(struct net_devic
dev->type = ARPHRD_SLIP;
dev->tx_queue_len = 100;
dev->flags = IFF_POINTOPOINT | IFF_NOARP;
- SET_MODULE_OWNER(dev);
}
next prev parent reply other threads:[~2007-12-04 10:33 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-04 5:08 Linux 2.6.24-rc4 Linus Torvalds
2007-12-04 10:23 ` [build failure] Re: Linux 2.6.24-rc4 on S390x Kamalesh Babulal
2007-12-04 10:31 ` Martin Schwidefsky
2007-12-04 10:32 ` Ingo Molnar [this message]
2007-12-04 13:22 ` Linux 2.6.24-rc4 Nicolas Pitre
2007-12-04 16:04 ` Jeff Garzik
2007-12-04 14:07 ` [local DoS] " Luiz Fernando N. Capitulino
2007-12-04 15:56 ` Linus Torvalds
2007-12-04 16:00 ` Ingo Molnar
2007-12-04 16:04 ` Luiz Fernando N. Capitulino
2007-12-04 16:08 ` Ingo Molnar
2007-12-04 16:18 ` [git pull] scheduler fixes Ingo Molnar
2007-12-04 16:40 ` Luiz Fernando N. Capitulino
2007-12-04 18:28 ` Greg KH
2007-12-04 18:41 ` Luiz Fernando N. Capitulino
2007-12-04 21:04 ` Ingo Molnar
2007-12-04 20:51 ` Linux 2.6.24-rc4 Maciej Rutecki
2007-12-04 21:06 ` Linus Torvalds
2007-12-04 21:19 ` Maciej Rutecki
2007-12-04 21:23 ` ATA ACPI (was Re: Linux 2.6.24-rc4) Jeff Garzik
2007-12-04 21:25 ` Jeff Garzik
2007-12-04 21:25 ` Alan Cox
2007-12-04 21:27 ` Jeff Garzik
2007-12-04 22:48 ` Maciej Rutecki
2007-12-04 23:00 ` Jeff Garzik
2007-12-05 7:46 ` Maciej Rutecki
2007-12-10 8:42 ` Tejun Heo
2007-12-05 0:23 ` Linux 2.6.24-rc4 Diego Calleja
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=20071204103237.GA15038@elte.hu \
--to=mingo@elte.hu \
--cc=akpm@linux-foundation.org \
--cc=apw@shadowen.org \
--cc=balbir@linux.vnet.ibm.com \
--cc=braunu@de.ibm.com \
--cc=jeff@garzik.org \
--cc=kamalesh@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=ptiedem@de.ibm.com \
--cc=torvalds@linux-foundation.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.