From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from eggs.gnu.org ([2001:4830:134:3::10]:56406)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <riku.voipio@linaro.org>) id 1XJIaR-0006AH-A5
	for qemu-devel@nongnu.org; Mon, 18 Aug 2014 04:46:48 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <riku.voipio@linaro.org>) id 1XJIaM-0006QJ-Fq
	for qemu-devel@nongnu.org; Mon, 18 Aug 2014 04:46:43 -0400
Received: from mail-yh0-f47.google.com ([209.85.213.47]:38056)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <riku.voipio@linaro.org>) id 1XJIaM-0006QD-BY
	for qemu-devel@nongnu.org; Mon, 18 Aug 2014 04:46:38 -0400
Received: by mail-yh0-f47.google.com with SMTP id f10so4218204yha.6
	for <qemu-devel@nongnu.org>; Mon, 18 Aug 2014 01:46:37 -0700 (PDT)
MIME-Version: 1.0
In-Reply-To: <CAFEAcA8kqdZzbtoUPEpVMMwaL0qAf0pvrOHyCA5PBrggRmx8fQ@mail.gmail.com>
References: <cover.1408100160.git.riku.voipio@linaro.org>
	<CAFEAcA8kqdZzbtoUPEpVMMwaL0qAf0pvrOHyCA5PBrggRmx8fQ@mail.gmail.com>
Date: Mon, 18 Aug 2014 11:46:36 +0300
Message-ID: <CAAqcGHmw5faSyib9M+sDXMGC4xYO+9Ykn33SH=U+cXXvOcAJ5g@mail.gmail.com>
From: Riku Voipio <riku.voipio@linaro.org>
Content-Type: text/plain; charset=UTF-8
Subject: Re: [Qemu-devel] [PULL 00/24] Linux-user updates
List-Id: <qemu-devel.nongnu.org>
List-Unsubscribe: <https://lists.nongnu.org/mailman/options/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.nongnu.org/archive/html/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <https://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: Peter Maydell <peter.maydell@linaro.org>, joakim.tjernlund@transmode.se
Cc: QEMU Developers <qemu-devel@nongnu.org>

On 15 August 2014 20:49, Peter Maydell <peter.maydell@linaro.org> wrote:
> On 15 August 2014 12:01,  <riku.voipio@linaro.org> wrote:
>> A usual set of improvements and bugfixes. The binfmt flag addition is an
>> ABI break so endusers need to update their binfmt registering scripts.

> Ugh, really? I didn't realize that when I saw that patch
> go past; I'd like to look at it in more detail before I
> apply this, since "break everybody's working setup"
> doesn't seem like a great idea...

Ok, I think Joakim's patch can be adjusted so that it continues to
work as-is with
current binfmt registrations that don't have "P" set. Meanwhile, I'll
drop the patch from this round and re-submit the current linux-user
que without it.

Riku