All of lore.kernel.org
 help / color / mirror / Atom feed
From: Laurent Vivier <laurent@vivier.eu>
To: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>,
	qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 1/2] linux-user: Update m68k syscall definitions to match Linux 4.4.
Date: Thu, 24 Dec 2015 22:14:37 +0100	[thread overview]
Message-ID: <567C603D.5080105@vivier.eu> (raw)
In-Reply-To: <1450983599-6060-1-git-send-email-glaubitz@physik.fu-berlin.de>



Le 24/12/2015 19:59, John Paul Adrian Glaubitz a écrit :
> Signed-off-by: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>
> ---
>  linux-user/m68k/syscall_nr.h | 27 +++++++++++++++++++++++++++
>  1 file changed, 27 insertions(+)
> 
> diff --git a/linux-user/m68k/syscall_nr.h b/linux-user/m68k/syscall_nr.h
> index 25f8521..a2daba0 100644
> --- a/linux-user/m68k/syscall_nr.h
> +++ b/linux-user/m68k/syscall_nr.h
> @@ -349,3 +349,30 @@
>  #define TARGET_NR_process_vm_writev     346
>  #define TARGET_NR_kcmp                  347
>  #define TARGET_NR_finit_module          348
> +#define TARGET_NR_sched_setattr         349
> +#define TARGET_NR_sched_getattr         350
> +#define TARGET_NR_renameat2             351
> +#define TARGET_NR_getrandom             352
> +#define TARGET_NR_memfd_create          353
> +#define TARGET_NR_bpf                   354
> +#define TARGET_NR_execveat              355
> +#define TARGET_NR_socket                356
> +#define TARGET_NR_socketpair            357
> +#define TARGET_NR_bind                  358
> +#define TARGET_NR_connect               359
> +#define TARGET_NR_listen                360
> +#define TARGET_NR_accept4               361
> +#define TARGET_NR_getsockopt            362
> +#define TARGET_NR_setsockopt            363
> +#define TARGET_NR_getsockname           364
> +#define TARGET_NR_getpeername           365
> +#define TARGET_NR_sendto                366
> +#define TARGET_NR_sendmsg               367
> +#define TARGET_NR_recvfrom              368
> +#define TARGET_NR_recvmsg               369
> +#define TARGET_NR_shutdown              370
> +#define TARGET_NR_recvmmsg              371
> +#define TARGET_NR_sendmmsg              372
> +#define TARGET_NR_userfaultfd           373
> +#define TARGET_NR_membarrier            374
> +#define TARGET_NR_mlock2                375
> 

Reviewed-by: Laurent Vivier <laurent@vivier.eu>

      parent reply	other threads:[~2015-12-24 21:14 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-24 18:59 [Qemu-devel] [PATCH 1/2] linux-user: Update m68k syscall definitions to match Linux 4.4 John Paul Adrian Glaubitz
2015-12-24 18:59 ` [Qemu-devel] [PATCH 2/2] linux-user: Add SOCKOP_sendmmsg and SOCKOP_recvmmsg socket call, wire them up John Paul Adrian Glaubitz
2015-12-24 21:16   ` Laurent Vivier
2015-12-24 19:04 ` [Qemu-devel] [PATCH 1/2] linux-user: Update m68k syscall definitions to match Linux 4.4 John Paul Adrian Glaubitz
2015-12-24 21:21   ` Laurent Vivier
2015-12-25  0:02     ` John Paul Adrian Glaubitz
2016-01-11 13:46   ` Riku Voipio
2016-01-11 13:54     ` Laurent Vivier
2016-01-11 13:57       ` John Paul Adrian Glaubitz
2016-01-11 14:10       ` Riku Voipio
2016-01-11 14:13         ` John Paul Adrian Glaubitz
2015-12-24 21:14 ` Laurent Vivier [this message]

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=567C603D.5080105@vivier.eu \
    --to=laurent@vivier.eu \
    --cc=glaubitz@physik.fu-berlin.de \
    --cc=qemu-devel@nongnu.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.