From: Greg Ungerer <gerg@snapgear.com>
To: uClinux development list <uclinux-dev@uclinux.org>
Cc: Linux/m68k <linux-m68k@lists.linux-m68k.org>,
Greg Ungerer <gerg@uclinux.org>,
Linux Kernel Development <linux-kernel@vger.kernel.org>
Subject: Re: [uClinux-dev] [PATCH] m68k, m68knommu: Wire up fanotify_init, fanotify_mark, and prlimit64
Date: Fri, 20 Aug 2010 13:38:36 +1000 [thread overview]
Message-ID: <4C6DF8BC.8060803@snapgear.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1008191804480.16652@ayla.of.borg>
Geert Uytterhoeven wrote:
> Signed-off-by: Geert Uytterhoeven <geert@linux-m68k.org>
Acked-by: Greg Ungerer <gerg@uclinux.org>
> ---
> arch/m68k/include/asm/unistd.h | 5 ++++-
> arch/m68k/kernel/entry.S | 3 +++
> arch/m68knommu/kernel/syscalltable.S | 3 +++
> 3 files changed, 10 insertions(+), 1 deletions(-)
>
> diff --git a/arch/m68k/include/asm/unistd.h b/arch/m68k/include/asm/unistd.h
> index 60b15d0..b43b36b 100644
> --- a/arch/m68k/include/asm/unistd.h
> +++ b/arch/m68k/include/asm/unistd.h
> @@ -340,10 +340,13 @@
> #define __NR_set_thread_area 334
> #define __NR_atomic_cmpxchg_32 335
> #define __NR_atomic_barrier 336
> +#define __NR_fanotify_init 337
> +#define __NR_fanotify_mark 338
> +#define __NR_prlimit64 339
>
> #ifdef __KERNEL__
>
> -#define NR_syscalls 337
> +#define NR_syscalls 340
>
> #define __ARCH_WANT_IPC_PARSE_VERSION
> #define __ARCH_WANT_OLD_READDIR
> diff --git a/arch/m68k/kernel/entry.S b/arch/m68k/kernel/entry.S
> index 2391bdf..6360c43 100644
> --- a/arch/m68k/kernel/entry.S
> +++ b/arch/m68k/kernel/entry.S
> @@ -765,4 +765,7 @@ sys_call_table:
> .long sys_set_thread_area
> .long sys_atomic_cmpxchg_32 /* 335 */
> .long sys_atomic_barrier
> + .long sys_fanotify_init
> + .long sys_fanotify_mark
> + .long sys_prlimit64
>
> diff --git a/arch/m68knommu/kernel/syscalltable.S b/arch/m68knommu/kernel/syscalltable.S
> index b30b3eb..79b1ed1 100644
> --- a/arch/m68knommu/kernel/syscalltable.S
> +++ b/arch/m68knommu/kernel/syscalltable.S
> @@ -355,6 +355,9 @@ ENTRY(sys_call_table)
> .long sys_set_thread_area
> .long sys_atomic_cmpxchg_32 /* 335 */
> .long sys_atomic_barrier
> + .long sys_fanotify_init
> + .long sys_fanotify_mark
> + .long sys_prlimit64
>
> .rept NR_syscalls-(.-sys_call_table)/4
> .long sys_ni_syscall
--
------------------------------------------------------------------------
Greg Ungerer -- Principal Engineer EMAIL: gerg@snapgear.com
SnapGear Group, McAfee PHONE: +61 7 3435 2888
8 Gardner Close FAX: +61 7 3217 5323
Milton, QLD, 4064, Australia WEB: http://www.SnapGear.com
parent reply other threads:[~2010-08-20 3:38 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <alpine.DEB.2.00.1008191804480.16652@ayla.of.borg>]
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=4C6DF8BC.8060803@snapgear.com \
--to=gerg@snapgear.com \
--cc=gerg@uclinux.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-m68k@lists.linux-m68k.org \
--cc=uclinux-dev@uclinux.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