All of lore.kernel.org
 help / color / mirror / Atom feed
From: Geoff Keating <geoffk@cygnus.com>
To: Franz.Sirl-kernel@lauterbach.com
Cc: drepper@cygnus.com, libc-alpha@sources.redhat.com,
	linuxppc-dev@lists.linuxppc.org
Subject: Re: [RFC] IPC64 with glibc-2.2 and linux-2.4
Date: Mon, 25 Sep 2000 14:24:09 -0700	[thread overview]
Message-ID: <200009252124.OAA25434@geoffk.org> (raw)
In-Reply-To: <5.0.0.19.2.20000925110119.01fe1df0@mail.lauterbach.com> (message from Franz Sirl on Mon, 25 Sep 2000 11:10:45 +0200)


> Date: Mon, 25 Sep 2000 11:10:45 +0200
> From: Franz Sirl <Franz.Sirl-kernel@lauterbach.com>
> Cc: libc-alpha@sources.redhat.com, linuxppc-dev@lists.linuxppc.org

> Yeah, I know. But it's no problem for me to push this change into the
> kernel after some people (including you :-)) have agreed to the principle
> of the patch.

I too agree with the principle of the patch.  There's no reason to
limit this quantity to 16 bits.

> 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...

I can't see any particular reason.

Did you test it?  There are four combinations to check:

new application/new kernel
old application/new kernel  (to test symbol versioning)
new application/old kernel  (test translation of old structure to new)
old application/old kernel  (this should Just Work if the above cases work)
			    (but of course you should still check it :-) )

--
- Geoffrey Keating <geoffk@cygnus.com>

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

  parent reply	other threads:[~2000-09-25 21:24 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
2000-09-25 15:54           ` Franz Sirl
2000-09-25 16:08             ` Ulrich Drepper
2000-09-25 21:24         ` Geoff Keating [this message]
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=200009252124.OAA25434@geoffk.org \
    --to=geoffk@cygnus.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.