From: Andreas Jaeger <aj@suse.de>
To: drepper@cygnus.com (Ulrich Drepper)
Cc: GNU libc hacker <libc-hacker@sourceware.cygnus.com>
Subject: Re: anybody handling the LCK64 stuff?
Date: Tue, 14 Dec 1999 01:44:00 -0000 [thread overview]
Message-ID: <u8aend980y.fsf@gromit.rhein-neckar.de> (raw)
In-Reply-To: <m3r9gqg35b.fsf@localhost.localnet>
>>>>> Ulrich Drepper writes:
> Can anybody handle adding the LCK64 stuff? I think it will have to be
> similar to the truncate64 code where we fall back on the LCK methods
> if the kernel is not supporting it.
The patch didn't go into 2.3.32 final - and it had some problems.
For Mips, the numbers were wrong. There were duplicates:
#define F_GETLK 14
#define F_SETLKW64 14
And there were no defines and no structure for Sparc32.
Ok, let's wait for 2.3.33. If it will be in 2.3.33, I make a patch.
Andreas
--
Andreas Jaeger
SuSE Labs aj@suse.de
private aj@arthur.rhein-neckar.de
prev parent reply other threads:[~1999-12-14 1:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-12-13 9:32 Ulrich Drepper
1999-12-13 11:30 ` Andreas Jaeger
1999-12-14 1:44 ` Andreas Jaeger [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=u8aend980y.fsf@gromit.rhein-neckar.de \
--to=aj@suse.de \
--cc=drepper@cygnus.com \
--cc=libc-hacker@sourceware.cygnus.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).