From: Roberto Nibali <ratz@drugphish.ch>
To: Pete Zaitcev <zaitcev@redhat.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] s390 (8/8): export sys_wait4.
Date: Fri, 13 Dec 2002 01:05:32 +0100 [thread overview]
Message-ID: <3DF9244C.7080705@drugphish.ch> (raw)
In-Reply-To: 20021212181747.B28477@devserv.devel.redhat.com
>>>>+EXPORT_SYMBOL(sys_wait4);
>>>
>>>Martin, hold on just a second. Last I checked, sys_wait4 was
>>>used ONLY by a moronic code in ipvs, _and_ there was a comment
>>>by the author above it "we are too lazy to do it properly".
>>>Do you have a better reason to export it?
>>
>>Guess I'm the malefactor this time since I've sent this patch to Martin
>>after some email exchanges with a guy that wanted LVS to work on a s390.
>>I reckon I will fix the said moronic code to use a syscall wrapper for
>>sys_wait4() so we don't step on anyone's toes.
>
> I should not have called it moronic. Everyone has schedule
Don't worry about it. We haven't always been too kind with lost RH
piranha users in the past either ;).
> constraints. I am wondering though, if the LVS and ipvs
> module are maintained actively. Perhaps I owe them a patch.
LVS and its kernel modules are definitely actively maintained all the
way from 2.2.x to 2.5.x kernels and if you want I'll make you a 2.0.x
kernel version too. It's just that recently everybody got a bit busy and
thus new releases tend to follow each other in increasing time intervals.
A patch would always be very welcome of course.
Best regards,
Roberto Nibali, ratz
--
echo '[q]sa[ln0=aln256%Pln256/snlbx]sb3135071790101768542287578439snlbxq'|dc
next prev parent reply other threads:[~2002-12-12 23:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-12 19:26 [PATCH] s390 (8/8): export sys_wait4 Pete Zaitcev
2002-12-12 21:19 ` Roberto Nibali
2002-12-12 23:17 ` Pete Zaitcev
2002-12-13 0:05 ` Roberto Nibali [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-12-12 18:10 Martin Schwidefsky
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=3DF9244C.7080705@drugphish.ch \
--to=ratz@drugphish.ch \
--cc=linux-kernel@vger.kernel.org \
--cc=zaitcev@redhat.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