linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Ulrich Drepper <drepper@redhat.com>
To: Franz Sirl <Franz.Sirl-kernel@lauterbach.com>
Cc: libc-alpha@sources.redhat.com, linuxppc-dev@lists.linuxppc.org
Subject: Re: [RFC] IPC64 with glibc-2.2 and linux-2.4
Date: 25 Sep 2000 08:25:54 -0700	[thread overview]
Message-ID: <m366nko5ml.fsf@otr.mynet.cygnus.com> (raw)
In-Reply-To: Franz Sirl's message of "Mon, 25 Sep 2000 11:10:45 +0200"


Franz Sirl <Franz.Sirl-kernel@lauterbach.com> writes:

> What about 'seq'? Can I safely bump it to 32bit for userspace in the final
> patch? I see no need for the kernel and userspace being different here, but
> all other archs are limiting it to 16bit, so there may be a reason...

You should avoid changing the size of the struct.  I haven't done the
math on this.

--
---------------.                          ,-.   1325 Chesapeake Terrace
Ulrich Drepper  \    ,-------------------'   \  Sunnyvale, CA 94089 USA
Red Hat          `--' drepper at redhat.com   `------------------------

** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

  reply	other threads:[~2000-09-25 15:25 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <Franz Sirl's message of "Mon, 25 Sep 2000 11:10:45 +0200">
     [not found] ` <Franz Sirl's message of "Sun, 24 Sep 2000 21:50:44 +0200">
2000-09-24 19:50   ` [RFC] IPC64 with glibc-2.2 and linux-2.4 Franz Sirl
2000-09-25  6:51     ` Ulrich Drepper
2000-09-25  9:10       ` Franz Sirl
2000-09-25 15:25         ` Ulrich Drepper [this message]
2000-09-25 15:54           ` Franz Sirl
2000-09-25 16:08             ` Ulrich Drepper
2000-09-25 21:24         ` Geoff Keating
2000-09-26 21:24           ` Franz Sirl
2000-09-27  0:45             ` Geoff Keating
2000-09-26  2:38 Jack Howarth

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=m366nko5ml.fsf@otr.mynet.cygnus.com \
    --to=drepper@redhat.com \
    --cc=Franz.Sirl-kernel@lauterbach.com \
    --cc=drepper@cygnus.com \
    --cc=libc-alpha@sources.redhat.com \
    --cc=linuxppc-dev@lists.linuxppc.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;
as well as URLs for NNTP newsgroup(s).