mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jamie Lokier <lk@tantalophile.demon.co.uk>
To: linux-kernel@vger.kernel.org
Cc: linux@arm.linux.org.uk
Subject: Re: ARM port missing pivot_root syscall
Date: Mon, 2 Apr 2001 16:43:58 +0200	[thread overview]
Message-ID: <20010402164358.A17735@pcep-jamie.cern.ch> (raw)
In-Reply-To: <20010402141918.A17334@pcep-jamie.cern.ch> <200104021358.OAA18003@tallyho.bc.nu>
In-Reply-To: <200104021358.OAA18003@tallyho.bc.nu>; from rmk@tallyho.bc.nu on Mon, Apr 02, 2001 at 02:58:23PM +0100

Russell King wrote:
> > A few months ago a colleague was frustrated to find pivot_root missing
> > from the ARM port.  Semi-standard C programs that use this call would
> > not compile for the ARM.  Perhaps you ARM folks would like to add it?
> 
> The missing system calls got added in the latest kernel.

Ok, good.

> > On this general theme, there are other constants, whose names are not
> > arch-specific but whose _values_ are arch-specific.  E.g. look in
> > <asm/fcntl.h>.  In most cases, some of the values are required for
> > historical compatibility, sometimes with other operating systems.
> 
> I don't see any missing constants in fcntl.h, compared with x86.  Which
> kernel version are you using?

I'm not aware of any other missing constants.

Just, having seen the missing syscalls which were presumably accidental,
I put forward that someone might wish to audit the other architectures
for missing definitions from other arch-specific header files.  Not just
asm/fcntl.h, but also e.g. asm/termios.h and others.  The idea is not
specific to the ARM port.

-- Jamie




      reply	other threads:[~2001-04-02 14:46 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-04-02 12:19 Jamie Lokier
2001-04-02 13:58 ` Russell King
2001-04-02 14:43   ` Jamie Lokier [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=20010402164358.A17735@pcep-jamie.cern.ch \
    --to=lk@tantalophile.demon.co.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@arm.linux.org.uk \
    /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

all inboxes | Powered by JetHome®