qemu-devel.nongnu.org archive mirror
 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:21:17 +0100	[thread overview]
Message-ID: <567C61CD.7040304@vivier.eu> (raw)
In-Reply-To: <567C41C6.6030500@physik.fu-berlin.de>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256



Le 24/12/2015 20:04, John Paul Adrian Glaubitz a écrit :
> 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.

I think you should have added this description in the commit message
of the patch.

You can also create your patch series with "git format-patch -n
- --cover-letter" to have a "[PATCH 0/2]" mail template to describe your
series.

Thanks,
Laurent

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQIcBAEBCAAGBQJWfGHNAAoJEPMMOL0/L748kX8QAJYs62/Uge60BbaBhBWBPNEL
AT1YzgnLN6yDUXl/rv538DyMoWnxxe5FkM4mc/fV3Wo84nHAAI61IwmdcxivPvXQ
0PHe0hNIaH4T8E0zQyVY85r983QQyYldpeW8kBGp/KhegEmpQDxyeIplPht6sZNI
zRuDHNP6xSNm+W6giPr0vK0RrUNQ2OdAKYNIKskrLS1u9p2pTzk7X0AXEhJjMHQX
ZoFkQYQX8cnWm3L5k6HCFIx6N0lVNfu6TClLq13Qo2XkRwR/ckWfgzXtdkZmyIBE
5E/0Fn69wNz4TbuQDKQc4Ef8OYC00eyhpV03d6Yt0+eb4yiUgayI620Ji6SVnvZw
edSwnvYVlQ7g6FqppiL7eXlXopOFBR7qMNWhdjtAsfSRh+XbAAf7IkPaYay4kJKE
j9XCeMimaqJdRBbbsVqd5okmkb86hlfriHpn1jsa9tHuTKJdgy4oDjmo7mDLB/uT
jmOWdlC/+/+huEI95mCahLt4Nz4G/7ikyFQYDZKFPa+nJzZLdV2SxZ8NNGG5ZlPt
2BoxDYVicN+VlVYDclDDu5yRM1TFH6zWAhs/dC1e2l7c4Ty1e5hTWoJgYUukXZxJ
gxq81DH2M57TjFvZsek80S/raiBGYYLd14Edau+I4JZd1XPuN0IlzWtSMC2J/eDG
jdPrS3fEJTE/5t+rT9T8
=aRxF
-----END PGP SIGNATURE-----

  reply	other threads:[~2015-12-24 21:21 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 [this message]
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=567C61CD.7040304@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 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).