From: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>
To: qemu-devel@nongnu.org
Cc: laurent@vivier.eu
Subject: Re: [Qemu-devel] [PATCH 1/2] linux-user: Update m68k syscall definitions to match Linux 4.4.
Date: Thu, 24 Dec 2015 20:04:38 +0100 [thread overview]
Message-ID: <567C41C6.6030500@physik.fu-berlin.de> (raw)
In-Reply-To: <1450983599-6060-1-git-send-email-glaubitz@physik.fu-berlin.de>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Hi Laurent!
Here are, as discussed previously, my proposed patches which change the
following:
PATCH 1/2 updates the syscall table for m68k to match Linux 4.4. This
one should be very obvious.
PATCH 2/2 adds the definitions for the socket calls SOCKOP_sendmmsg and
SOCKOP_recvmmsg and wires them up with the rest of the code. The
necessary function do_sendrecvmmsg() is already present in
linux-user/syscall.c. After adding these two definitions and wiring them
up, I no longer receive an error message about the unimplemented socket
calls when running "apt-get update" on Debian unstable running on qemu
with glibc_2.21 on m68k.
Cheers,
Adrian
- --
.''`. John Paul Adrian Glaubitz
: :' : Debian Developer - glaubitz@debian.org
`. `' Freie Universitaet Berlin - glaubitz@physik.fu-berlin.de
`- GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2
iQIcBAEBCAAGBQJWfEHBAAoJEHQmOzf1tfkTE8MQAL8csEYAtrrMy1VQlQOBj4rV
+yLUkCRYobisEplXl9mQrgJ3ATswJYvj5C2wfU6wAlzUkHoLLZ/IbJwHDY9DhplN
GlkzHqjpp7mhf8lngsrdyQqmD+06ebEGvnXA8/4xwY7zVsYpddRt31ThYBvUTrbt
OwmttTypOry9aivitjBEUehpPPa82h4bc2/Jc90THyxbbb0t90MHSTsh42wY9JPT
5ePBcMSjjXi3lab7DWyPBgT0vDEDez0WhP3xbGKP4/nRKQcdJhwxxa1yBydIgEKT
WbzOUBydO6OjeX4ZYza+gLcKqRrhqokXuUW77CLrXlv+gwon3oI4m66zUq1J1xZz
kNIe5bdIPQbJ9ShCWuvbL7y0EFH/s6IOf8dcLtX/rnJ6/QvXuZJk3j3lrIn1BHK8
7aK/I1QkPvFAl3SCpi4XkEemuvKNkgDiK73WzgKHbfBSpx8UqoXH6ws4x6hhYJEv
QvN92VPj8KTUxmtG+Lhbi/yS7kowXk4N8RO3zWU4Ul94KY8PFYVIPqkyC/DcN94F
I7a7uqKrWxurzksPLsSMhmIyY5F/vik3Kw3I7Wo9+1/qB0KhCMtFTJwefLZnWoj/
2UrjE6wItlJIvMOGHt+Ih4UrXRp52PwcAcHyM7F+fhwvN5mQvtzNJehYuM/JQJZP
qXHC3MwjACFQJme1O2KT
=oAZC
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2015-12-24 19:04 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 ` John Paul Adrian Glaubitz [this message]
2015-12-24 21:21 ` [Qemu-devel] [PATCH 1/2] linux-user: Update m68k syscall definitions to match Linux 4.4 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
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=567C41C6.6030500@physik.fu-berlin.de \
--to=glaubitz@physik.fu-berlin.de \
--cc=laurent@vivier.eu \
--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 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).