public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Russell King <rmk+lkml@arm.linux.org.uk>
To: Valdis.Kletnieks@vt.edu
Cc: Martin Michlmayr <tbm@cyrius.com>,
	linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.arm.linux.org.uk
Subject: Re: AUDIT=y build failure on ARM
Date: Thu, 21 Sep 2006 17:25:44 +0100	[thread overview]
Message-ID: <20060921162543.GA29714@flint.arm.linux.org.uk> (raw)
In-Reply-To: <200609211144.k8LBiGjY018080@turing-police.cc.vt.edu>

On Thu, Sep 21, 2006 at 07:44:16AM -0400, Valdis.Kletnieks@vt.edu wrote:
> On Wed, 20 Sep 2006 14:49:08 +0200, Martin Michlmayr said:
> > I get the build failure below with AUDIT=y on ARM.  The problem is
> > that lib/audit.c includes asm-generic/audit_dir_write.h which lists a
> > number of syscalls that are not defined on ARM (and some other platforms).
> 
> And somebody (I forget who) was complaining that some debugging tool was only available
> on the x86/sparc/ppc families of CPUs, and didn't like Alan Cox's suggestion
> that they go add it.
> 
> Given that missing an entire class of syscall (the *at flavors) on an
> architecture isn't a deterrent to inclusion, Alan's response was totally
> on-target....
> 
> (I'm presuming the usual reason for such missing syscalls is that nobody
> has bothered trying to run software that uses a *at call on an ARM, so
> nobody's bothered wiring them up and thereby increasing the kernel image
> size on a platform where it's likely to be *very* important?)

They probably should be wired up, but TBH I _always_ miss the addition
of such things.  I don't remember there being any notification to arch
maintainers that something was due to be done.

-- 
Russell King
 Linux kernel    2.6 ARM Linux   - http://www.arm.linux.org.uk/
 maintainer of:  2.6 Serial core

      reply	other threads:[~2006-09-21 16:25 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-20 12:49 AUDIT=y build failure on ARM Martin Michlmayr
2006-09-21 11:44 ` Valdis.Kletnieks
2006-09-21 16:25   ` Russell King [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=20060921162543.GA29714@flint.arm.linux.org.uk \
    --to=rmk+lkml@arm.linux.org.uk \
    --cc=Valdis.Kletnieks@vt.edu \
    --cc=linux-arm-kernel@lists.arm.linux.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tbm@cyrius.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