public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg Ungerer <gerg@snapgear.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Linux/m68k <linux-m68k@vger.kernel.org>,
	Greg Ungerer <gerg@uclinux.org>,
	Linux Kernel Development <linux-kernel@vger.kernel.org>,
	uClinux list <uclinux-dev@uclinux.org>
Subject: Re: m68k,m68knommu: Wire up name_to_handle_at, open_by_handle_at, clock_adjtime
Date: Mon, 21 Mar 2011 17:16:12 +1000	[thread overview]
Message-ID: <4D86FB3C.8030504@snapgear.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1103201310110.6574@ayla.of.borg>

On 20/03/11 22:11, Geert Uytterhoeven wrote:
> Signed-off-by: Geert Uytterhoeven<geert@linux-m68k.org>

Looks good:

Acked-by: Greg Ungerer <gerg@uclinux.org>

Regards
Greg



> ---
>   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 26d851d..f69f7ce 100644
> --- a/arch/m68k/include/asm/unistd.h
> +++ b/arch/m68k/include/asm/unistd.h
> @@ -343,10 +343,13 @@
>   #define __NR_fanotify_init	337
>   #define __NR_fanotify_mark	338
>   #define __NR_prlimit64		339
> +#define __NR_name_to_handle_at	340
> +#define __NR_open_by_handle_at	341
> +#define __NR_clock_adjtime	342
>
>   #ifdef __KERNEL__
>
> -#define NR_syscalls		340
> +#define NR_syscalls		343
>
>   #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 1559dea..8f9524a 100644
> --- a/arch/m68k/kernel/entry.S
> +++ b/arch/m68k/kernel/entry.S
> @@ -750,4 +750,7 @@ sys_call_table:
>   	.long sys_fanotify_init
>   	.long sys_fanotify_mark
>   	.long sys_prlimit64
> +	.long sys_name_to_handle_at	/* 340 */
> +	.long sys_open_by_handle_at
> +	.long sys_clock_adjtime
>
> diff --git a/arch/m68knommu/kernel/syscalltable.S b/arch/m68knommu/kernel/syscalltable.S
> index 79b1ed1..605bbbe 100644
> --- a/arch/m68knommu/kernel/syscalltable.S
> +++ b/arch/m68knommu/kernel/syscalltable.S
> @@ -358,6 +358,9 @@ ENTRY(sys_call_table)
>   	.long sys_fanotify_init
>   	.long sys_fanotify_mark
>   	.long sys_prlimit64
> +	.long sys_name_to_handle_at	/* 340 */
> +	.long sys_open_by_handle_at
> +	.long sys_clock_adjtime
>
>   	.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

  reply	other threads:[~2011-03-21  7:22 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-20 12:11 Geert Uytterhoeven
2011-03-21  7:16 ` Greg Ungerer [this message]
  -- strict thread matches above, loose matches on Subject: below --
2011-03-20 12:28 m68k,m68knommu: Wire up name_to_handle_at, open_by_handle_at, clock_adjtime Geert Uytterhoeven

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=4D86FB3C.8030504@snapgear.com \
    --to=gerg@snapgear.com \
    --cc=geert@linux-m68k.org \
    --cc=gerg@uclinux.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-m68k@vger.kernel.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