public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Pete Zaitcev <zaitcev@redhat.com>
To: Kai Germaschewski <kai@tp1.ruhr-uni-bochum.de>
Cc: Pete Zaitcev <zaitcev@redhat.com>,
	Martin Schwidefsky <schwidefsky@de.ibm.com>,
	linux-kernel@vger.kernel.org
Subject: Re: Strange s390 code in 2.4.19-pre8
Date: Mon, 13 May 2002 12:32:37 -0400	[thread overview]
Message-ID: <20020513123237.C6208@devserv.devel.redhat.com> (raw)
In-Reply-To: <20020513122330.B6208@devserv.devel.redhat.com> <Pine.LNX.4.44.0205131125250.19498-100000@chaos.physics.uiowa.edu>

> Date: Mon, 13 May 2002 11:30:06 -0500 (CDT)
> From: Kai Germaschewski <kai@tp1.ruhr-uni-bochum.de>

> I think I see two easy way to resolve the problem:
> o backport the Rules.make change (it's been in 2.5 for months w/o even
>   anybody noticing it, so it's definitely stable)
> o Move the EXPORT_SYMBOL() in drivers/isdn/hisax/fsm.o into
>   drivers/isdn/hisax/config.o

If ISDN people are willing to do that, it would be a great
relief. I did not raise this question because undoubtedly
they were using fsm.c first, so it was s390 mistake (accorting
to the comment in the drivers/s390/net/fsm.c).

-- Pete

  reply	other threads:[~2002-05-13 16:33 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 [this message]
2002-05-13 17:39           ` Kai Germaschewski
2002-05-13 16:16 ` Kai Germaschewski
2002-05-13 16:19   ` Pete Zaitcev
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=20020513123237.C6208@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