From: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>
To: Riku Voipio <riku.voipio@iki.fi>, Laurent Vivier <laurent@vivier.eu>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 1/2] linux-user: Update m68k syscall definitions to match Linux 4.4.
Date: Mon, 11 Jan 2016 15:13:19 +0100 [thread overview]
Message-ID: <5693B87F.9000808@physik.fu-berlin.de> (raw)
In-Reply-To: <962384e6-1ee8-456a-a651-6371e8ecddbf@iki.fi>
On 01/11/2016 03:10 PM, Riku Voipio wrote:
> Ok, thanks for clarification, I had forgotten that m68k in mainline Qemu
> was coldfire only. I'll be happy to add debian/m68k to my tests when the
> support
> gets merged.
Laurent's master-dev branch seems to have improved quite a lot,
currently testing it. The networking issue has been resolved.
You need to apply both of my patches though as otherwise apt complains
about the missing socket calls 19/20.
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:13 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 [this message]
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=5693B87F.9000808@physik.fu-berlin.de \
--to=glaubitz@physik.fu-berlin.de \
--cc=laurent@vivier.eu \
--cc=qemu-devel@nongnu.org \
--cc=riku.voipio@iki.fi \
/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.