From: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>
To: riku.voipio@linaro.org, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PULL 16/17] linux-user: Add SOCKOP_sendmmsg and SOCKOP_recvmmsg socket call, wire them up.
Date: Mon, 11 Jan 2016 15:51:18 +0100 [thread overview]
Message-ID: <5693C166.3090804@physik.fu-berlin.de> (raw)
In-Reply-To: <5a53dc5042d9250f2011e54cd065ed360e34d2ac.1452521686.git.riku.voipio@linaro.org>
On 01/11/2016 03:16 PM, riku.voipio@linaro.org wrote:
> From: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>
Commit message / title should probably say "socket calls", not
"socket call" ;). If possible, please fix the grammar mistake :).
In any case, THANKS a lot for pulling in my changes!
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
next prev parent reply other threads:[~2016-01-11 14:51 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-11 14:16 [Qemu-devel] [PULL 00/17] linux-user queque riku.voipio
2016-01-11 14:16 ` [Qemu-devel] [PULL 01/17] linux-user: add signalfd/signalfd4 syscalls riku.voipio
2016-01-11 14:16 ` [Qemu-devel] [PULL 02/17] linux-user: correctly align target_epoll_event riku.voipio
2016-01-11 14:16 ` [Qemu-devel] [PULL 03/17] linux-user: in poll(), if nfds is 0, pfd can be NULL riku.voipio
2016-01-11 14:16 ` [Qemu-devel] [PULL 04/17] linux-user/syscall.c: malloc()/calloc() to g_malloc()/g_try_malloc()/g_new0() riku.voipio
2016-01-11 14:16 ` [Qemu-devel] [PULL 05/17] linux-user: SOCK_PACKET uses network endian to encode protocol in socket() riku.voipio
2016-01-11 14:16 ` [Qemu-devel] [PULL 06/17] linux-user: rename TargetFdFunc to TargetFdDataFunc, and structure fields accordingly riku.voipio
2016-01-11 14:16 ` [Qemu-devel] [PULL 07/17] linux-user: add a function hook to translate sockaddr riku.voipio
2016-01-11 14:16 ` [Qemu-devel] [PULL 08/17] linux-user: manage bind with a socket of SOCK_PACKET type riku.voipio
2016-01-11 14:16 ` [Qemu-devel] [PULL 09/17] linux-user: check fd is >= 0 in fd_trans_host_to_target_data/fd_trans_host_to_target_addr riku.voipio
2016-01-11 14:16 ` [Qemu-devel] [PULL 10/17] linux-user, sh4: fix signal retcode address riku.voipio
2016-01-11 14:16 ` [Qemu-devel] [PULL 11/17] linux-user/mmap.c: Always zero MAP_ANONYMOUS memory in mmap_frag() riku.voipio
2016-01-11 14:16 ` [Qemu-devel] [PULL 12/17] unicore32: convert get_sp_from_cpustate from macro to inline riku.voipio
2016-01-11 14:16 ` [Qemu-devel] [PULL 13/17] linux-user: enable sigaltstack for all architectures riku.voipio
2016-01-11 14:16 ` [Qemu-devel] [PULL 14/17] linux-user/syscall.c: Use SOL_SOCKET instead of level for setsockopt() riku.voipio
2016-01-11 14:16 ` [Qemu-devel] [PULL 15/17] linux-user: Update m68k syscall definitions to match Linux 4.4 riku.voipio
2016-01-11 14:16 ` [Qemu-devel] [PULL 16/17] linux-user: Add SOCKOP_sendmmsg and SOCKOP_recvmmsg socket call, wire them up riku.voipio
2016-01-11 14:51 ` John Paul Adrian Glaubitz [this message]
2016-01-11 14:16 ` [Qemu-devel] [PULL 17/17] linux-user/mmap.c: Use end instead of real_end in target_mmap riku.voipio
2016-01-11 15:12 ` [Qemu-devel] [PULL 00/17] linux-user queque Peter Maydell
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=5693C166.3090804@physik.fu-berlin.de \
--to=glaubitz@physik.fu-berlin.de \
--cc=qemu-devel@nongnu.org \
--cc=riku.voipio@linaro.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).