From: Andrew Donnellan <ajd@linux.ibm.com>
To: Rohan McLure <rmclure@linux.ibm.com>, linuxppc-dev@lists.ozlabs.org
Cc: npiggin@gmail.com
Subject: Re: [PATCH v2 06/14] powerpc: Include all arch-specific syscall prototypes
Date: Wed, 10 Aug 2022 15:57:09 +1000 [thread overview]
Message-ID: <0d0c1bde39b8129185f79d6ac93abde7ad08f2de.camel@linux.ibm.com> (raw)
In-Reply-To: <9109e768d3b7d141d1b0095773cd737bf9ae497c.camel@linux.ibm.com>
On Mon, 2022-08-08 at 15:24 +1000, Andrew Donnellan wrote:
> > diff --git a/arch/powerpc/include/asm/syscalls.h
> > b/arch/powerpc/include/asm/syscalls.h
> > index 025d4b877161..8b2757d7f423 100644
> > --- a/arch/powerpc/include/asm/syscalls.h
> > +++ b/arch/powerpc/include/asm/syscalls.h
> > @@ -8,49 +8,93 @@
> > #include <linux/types.h>
> > #include <linux/compat.h>
> >
> > +#ifdef CONFIG_PPC64
> > +#include <asm/ppc32.h>
> > +#endif
> > +#include <asm/unistd.h>
> > +#include <asm/ucontext.h>
> > +
> > struct rtas_args;
> >
> > -asmlinkage long sys_mmap(unsigned long addr, size_t len,
> > - unsigned long prot, unsigned long flags,
> > - unsigned long fd, off_t offset);
> > -asmlinkage long sys_mmap2(unsigned long addr, size_t len,
> > - unsigned long prot, unsigned long flags,
> > - unsigned long fd, unsigned long pgoff);
> > -asmlinkage long sys_ppc64_personality(unsigned long personality);
> > +#ifndef CONFIG_ARCH_HAS_SYSCALL_WRAPPER
Introduce this ifdef once it starts mattering at patch 10, I think.
--
Andrew Donnellan OzLabs, ADL Canberra
ajd@linux.ibm.com IBM Australia Limited
next prev parent reply other threads:[~2022-08-10 5:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-25 6:27 [PATCH v2 06/14] powerpc: Include all arch-specific syscall prototypes Rohan McLure
2022-08-08 5:24 ` Andrew Donnellan
2022-08-10 5:57 ` Andrew Donnellan [this message]
2022-08-08 9:56 ` Christophe Leroy
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=0d0c1bde39b8129185f79d6ac93abde7ad08f2de.camel@linux.ibm.com \
--to=ajd@linux.ibm.com \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=npiggin@gmail.com \
--cc=rmclure@linux.ibm.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;
as well as URLs for NNTP newsgroup(s).