linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg Ungerer <gerg@uclinux.org>
To: Geert Uytterhoeven <geert@linux-m68k.org>,
	Andreas Schwab <schwab@linux-m68k.org>
Cc: linux-m68k@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] [RFC] m68k: Wire up direct socket calls
Date: Mon, 7 Sep 2015 13:24:39 +1000	[thread overview]
Message-ID: <55ED0377.4020603@uclinux.org> (raw)
In-Reply-To: <1441533991-23853-1-git-send-email-geert@linux-m68k.org>

Hi Geert,

On 06/09/15 20:06, Geert Uytterhoeven wrote:
> Signed-off-by: Geert Uytterhoeven <geert@linux-m68k.org>

Both of these syscall patches look good to me:

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

Regards
Greg


> ---
>  arch/m68k/include/asm/unistd.h      |  2 +-
>  arch/m68k/include/uapi/asm/unistd.h | 15 +++++++++++++++
>  arch/m68k/kernel/syscalltable.S     | 16 +++++++++++++++-
>  3 files changed, 31 insertions(+), 2 deletions(-)
> 
> diff --git a/arch/m68k/include/asm/unistd.h b/arch/m68k/include/asm/unistd.h
> index 244e0dbe45dbeda3..47d6b7153960274e 100644
> --- a/arch/m68k/include/asm/unistd.h
> +++ b/arch/m68k/include/asm/unistd.h
> @@ -4,7 +4,7 @@
>  #include <uapi/asm/unistd.h>
>  
>  
> -#define NR_syscalls		356
> +#define NR_syscalls		371
>  
>  #define __ARCH_WANT_OLD_READDIR
>  #define __ARCH_WANT_OLD_STAT
> diff --git a/arch/m68k/include/uapi/asm/unistd.h b/arch/m68k/include/uapi/asm/unistd.h
> index 61fb6cb9d2ae3c66..bf168d5ec3d96d32 100644
> --- a/arch/m68k/include/uapi/asm/unistd.h
> +++ b/arch/m68k/include/uapi/asm/unistd.h
> @@ -361,5 +361,20 @@
>  #define __NR_memfd_create	353
>  #define __NR_bpf		354
>  #define __NR_execveat		355
> +#define __NR_socket		356
> +#define __NR_socketpair		357
> +#define __NR_bind		358
> +#define __NR_connect		359
> +#define __NR_listen		360
> +#define __NR_accept4		361
> +#define __NR_getsockopt		362
> +#define __NR_setsockopt		363
> +#define __NR_getsockname	364
> +#define __NR_getpeername	365
> +#define __NR_sendto		366
> +#define __NR_sendmsg		367
> +#define __NR_recvfrom		368
> +#define __NR_recvmsg		369
> +#define __NR_shutdown		370
>  
>  #endif /* _UAPI_ASM_M68K_UNISTD_H_ */
> diff --git a/arch/m68k/kernel/syscalltable.S b/arch/m68k/kernel/syscalltable.S
> index a0ec4303f2c8e57a..2cec7cdc8e440f08 100644
> --- a/arch/m68k/kernel/syscalltable.S
> +++ b/arch/m68k/kernel/syscalltable.S
> @@ -376,4 +376,18 @@ ENTRY(sys_call_table)
>  	.long sys_memfd_create
>  	.long sys_bpf
>  	.long sys_execveat		/* 355 */
> -
> +	.long sys_socket
> +	.long sys_socketpair
> +	.long sys_bind
> +	.long sys_connect
> +	.long sys_listen		/* 360 */
> +	.long sys_accept4
> +	.long sys_getsockopt
> +	.long sys_setsockopt
> +	.long sys_getsockname
> +	.long sys_getpeername		/* 365 */
> +	.long sys_sendto
> +	.long sys_sendmsg
> +	.long sys_recvfrom
> +	.long sys_recvmsg
> +	.long sys_shutdown		/* 370 */
> 


  parent reply	other threads:[~2015-09-07  3:21 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-06 10:06 [PATCH 1/2] [RFC] m68k: Wire up direct socket calls Geert Uytterhoeven
2015-09-06 10:06 ` [PATCH 2/2] m68k: Wire up userfaultfd Geert Uytterhoeven
2015-09-07  3:24 ` Greg Ungerer [this message]
2015-09-11  9:59 ` [PATCH 1/2] [RFC] m68k: Wire up direct socket calls 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=55ED0377.4020603@uclinux.org \
    --to=gerg@uclinux.org \
    --cc=geert@linux-m68k.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-m68k@vger.kernel.org \
    --cc=schwab@linux-m68k.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;
as well as URLs for NNTP newsgroup(s).