From: Keith Owens <kaos@ocs.com.au>
To: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] iget-locked [2/6]
Date: Sat, 11 May 2002 13:28:04 +1000 [thread overview]
Message-ID: <4362.1021087684@ocs3.intra.ocs.com.au> (raw)
In-Reply-To: Your message of "Fri, 10 May 2002 22:06:46 EST." <Pine.LNX.4.44.0205102204040.11642-100000@chaos.physics.uiowa.edu>
On Fri, 10 May 2002 22:06:46 -0500 (CDT),
Kai Germaschewski <kai@tp1.ruhr-uni-bochum.de> wrote:
>On Sat, 11 May 2002, Keith Owens wrote:
>
>> True, but if the iget change goes into 2.5 it will probably be
>> backported to 2.4 later, 2.4 still has the restriction.
>
>It's a two line change to Rules.make, so I suppose that can be backported
>as well ;-)
The change looks safe enough for the kernel but I worry about its
impact on distributors who play silly buggers with the modversion
files (R**H** springs to mind). It would be polite to check with the
major distributors before backporting the change to 2.4.
>It's needed anyway IIRC, since s390 and ISDN both have fsm.o, and both do
>export symbols.
ISDN on s390. The mind boggles.
prev parent reply other threads:[~2002-05-11 3:28 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-10 16:07 Jan Harkes
2002-05-10 19:57 ` Alexander Viro
2002-05-10 20:00 ` Linus Torvalds
2002-05-10 20:15 ` Alexander Viro
2002-05-10 20:17 ` Linus Torvalds
2002-05-11 0:22 ` Keith Owens
2002-05-11 2:21 ` Kai Germaschewski
2002-05-11 2:48 ` Keith Owens
2002-05-11 3:04 ` Jan Harkes
2002-05-11 3:44 ` Alexander Viro
2002-05-11 9:23 ` Christoph Hellwig
2002-05-11 9:22 ` Christoph Hellwig
2002-05-11 3:06 ` Kai Germaschewski
2002-05-11 3:28 ` Keith Owens [this message]
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=4362.1021087684@ocs3.intra.ocs.com.au \
--to=kaos@ocs.com.au \
--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
all inboxes | Powered by JetHome®