From: Pete Zaitcev <zaitcev@redhat.com>
To: Kai Germaschewski <kai@tp1.ruhr-uni-bochum.de>
Cc: Martin Schwidefsky <schwidefsky@de.ibm.com>,
Pete Zaitcev <zaitcev@redhat.com>,
linux-kernel@vger.kernel.org
Subject: Re: Strange s390 code in 2.4.19-pre8
Date: Mon, 13 May 2002 12:19:33 -0400 [thread overview]
Message-ID: <20020513121933.A6208@devserv.devel.redhat.com> (raw)
In-Reply-To: <OFFA479633.3A335CB7-ONC1256BB8.002ABB8D@de.ibm.com> <Pine.LNX.4.44.0205131114420.19498-100000@chaos.physics.uiowa.edu>
> Date: Mon, 13 May 2002 11:16:07 -0500 (CDT)
> From: Kai Germaschewski <kai@tp1.ruhr-uni-bochum.de>
> > > #2 - strange changes to net Makefile
> > The intention of this is to have fsm.o built as a module if ctc
> > and iucv are built as modules too. I agree that this is broken
> > if one of {iucv,ctc} is built as a module and the other is built
> > in.
>
> Actually, I don't think it's broken, Rules.make takes care of that case
> and compiles fsm.o into the kernel in the latter case, it does not build
> a fsm.o module.
>
> --Kai
Obviously, the guy who did the change expected it to work
like you described, but he never tested it, and it doesn't.
ctc fails to load with init_fsm undefined.
It would work if EXPORT_SYMBOL_NOVERS were involved.
-- Pete
next prev parent reply other threads:[~2002-05-13 16:20 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-13 7:54 Strange s390 code in 2.4.19-pre8 Martin Schwidefsky
2002-05-13 16:10 ` Pete Zaitcev
2002-05-13 16:18 ` Kai Germaschewski
2002-05-13 16:23 ` Pete Zaitcev
2002-05-13 16:30 ` Kai Germaschewski
2002-05-13 16:32 ` Pete Zaitcev
2002-05-13 17:39 ` Kai Germaschewski
2002-05-13 16:16 ` Kai Germaschewski
2002-05-13 16:19 ` Pete Zaitcev [this message]
2002-05-13 16:25 ` Kai Germaschewski
2002-05-14 1:22 ` Keith Owens
-- strict thread matches above, loose matches on Subject: below --
2002-05-13 22:42 Ulrich Weigand
2002-05-13 22:50 ` Kai Germaschewski
2002-05-10 16:47 Pete Zaitcev
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=20020513121933.A6208@devserv.devel.redhat.com \
--to=zaitcev@redhat.com \
--cc=kai@tp1.ruhr-uni-bochum.de \
--cc=linux-kernel@vger.kernel.org \
--cc=schwidefsky@de.ibm.com \
/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