From: "U. George" <netbeans@gatworks.com>
To: Linux on Alpha processors <axp-list@redhat.com>
Cc: linux-kernel@vger.kernel.org, Jay Estabrook <jay.estabrook@hp.com>
Subject: Re: Question about F_RDLCK and F_WRLCK on alpha
Date: Wed, 14 Nov 2007 22:47:52 -0500 [thread overview]
Message-ID: <473BC168.4000206@gatworks.com> (raw)
In-Reply-To: <473B600E.9030703@linux-kernel.at>
I suppose this can be better analyzed if the cpp output is presented to
show exactly how rdlck/wrlck is included/defined .
But the only requirement is that the flags are unique. solong as wrlck
!= rdlck != unlck every is happy.
There is no expectation that an i386 binary will run on an alpha machine.
there might be an issue if the i386 source code uses "0" or "1"
constants instead of the WRLCK/RDLCK. And then compiled on the alpha.
Then it would be out of sync.
I suppose they are different bec the folks at OSF had it defined that
way. And there was some need to run OSF/alpha bins on a linux/alpha (
just a guess on my part )
Oliver Falk wrote:
> Hi!
>
> Can someone explain me, why we have different define's for WRLCK and
> RDLCK within alpha kernel headers:
prev parent reply other threads:[~2007-11-15 3:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-14 20:52 Question about F_RDLCK and F_WRLCK on alpha Oliver Falk
2007-11-15 3:47 ` U. George [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=473BC168.4000206@gatworks.com \
--to=netbeans@gatworks.com \
--cc=axp-list@redhat.com \
--cc=jay.estabrook@hp.com \
--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