From: Chandan Rajendra <chandan@linux.vnet.ibm.com>
To: linuxppc-dev@lists.ozlabs.org
Cc: Chris Packham <Chris.Packham@alliedtelesis.co.nz>,
Paul Mackerras <paulus@samba.org>
Subject: Re: syscall statx not implemented on powerpc
Date: Mon, 13 Mar 2017 14:21:47 +0530 [thread overview]
Message-ID: <4396749.JbYdqAFZXV@localhost.localdomain> (raw)
In-Reply-To: <7dba3a5469d34ac3890a5eaa16822a75@svr-chch-ex1.atlnz.lc>
On Monday, March 13, 2017 03:33:07 AM Chris Packham wrote:
> Hi,
>
> I've just attempted to build a powerpc kernel from 4.11-rc2 using a
> custom defconfig (available on request) and I'm hitting the following
> error in the early stages of compilation.
>
> <stdin>:1325:2: error: #warning syscall statx not implemented [-Werror=cpp]
>
> Same thing seems to happen with mpc85xx_basic_defconfig.
>
> I don't actually need this syscall so I'd be happy to turn something off
> to get things building. I did a quick search and couldn't see anything
> on linuxppc-dev but google keeps correcting "statx" to "stats" so I
> could have missed it.
>
>
The upstream commit
(https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=a528d35e8bfcc521d7cb70aaf03e1bd296c8493f)
that introduces the statx syscall provides a test program. I will wire-up the
syscall on ppc64, run that test program and post the patch if the test program
works well.
--
chandan
next prev parent reply other threads:[~2017-03-13 8:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-13 3:33 syscall statx not implemented on powerpc Chris Packham
2017-03-13 8:51 ` Chandan Rajendra [this message]
2017-03-13 20:01 ` Chris Packham
2017-03-14 11:57 ` Michael Ellerman
2017-03-14 19:31 ` Chris Packham
2017-03-15 0:08 ` Michael Ellerman
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=4396749.JbYdqAFZXV@localhost.localdomain \
--to=chandan@linux.vnet.ibm.com \
--cc=Chris.Packham@alliedtelesis.co.nz \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=paulus@samba.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