All of lore.kernel.org
 help / color / mirror / Atom feed
From: Laurent Vivier <laurent@vivier.eu>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: Riku Voipio <riku.voipio@iki.fi>,
	QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [PULL 0/1] Linux user for 5.0 patches
Date: Thu, 16 Apr 2020 21:15:20 +0200	[thread overview]
Message-ID: <90666b58-6e4e-8f4a-c27a-eed2ce2a73a3@vivier.eu> (raw)
In-Reply-To: <CAFEAcA-UWSJDvq5xmn2GTKY2zAgenkM7whdvn6FiY1+pUKBhcA@mail.gmail.com>

Le 16/04/2020 à 21:08, Peter Maydell a écrit :
> On Thu, 16 Apr 2020 at 18:16, Laurent Vivier <laurent@vivier.eu> wrote:
>>
>> Le 16/04/2020 à 18:03, Peter Maydell a écrit :
>>> On Thu, 16 Apr 2020 at 16:29, Laurent Vivier <laurent@vivier.eu> wrote:
>>>>
>>>> The following changes since commit 20038cd7a8412feeb49c01f6ede89e36c8995472:
>>>>
>>>>   Update version for v5.0.0-rc3 release (2020-04-15 20:51:54 +0100)
>>>>
>>>> are available in the Git repository at:
>>>>
>>>>   git://github.com/vivier/qemu.git tags/linux-user-for-5.0-pull-request
>>>>
>>>> for you to fetch changes up to 386d38656889a40d29b514ee6f34997ca18f741e:
>>>>
>>>>   linux-user/syscall.c: add target-to-host mapping for epoll_create1() (2020-04-16 09:24:22 +0200)
>>>>
>>>> ----------------------------------------------------------------
>>>> Fix epoll_create1() for qemu-alpha
>>>>
>>>> ----------------------------------------------------------------
>>>
>>> How critical is this bug fix? After rc3, I really don't want
>>> to have to create an rc4 unless it's unavoidable...
>>
>> See the launchpad bug (https://bugs.gentoo.org/717548): on alpha, it
>> prevents the use of python3 in gentoo chroot, and thus we can't use
>> emerge to install packages. It also impacts cmake on debian (see
>> https://bugs.launchpad.net/bugs/1860553).
>>
>> But it's not a regression, so up to you to reject it. It appears now
>> because most of the distro have switched from python2 to python3.
>>
>> It's a low risk change, only in linux-user and for archs that have a
>> different EPOLL_CLOEXEC value.
> 
> Thanks for the explanation. I think that I'll put it to one
> side and if we need an rc4 for some other reason it can go in,
> but it's not sufficiently major to merit an rc4 by itself.
> 

Thank you, I agree.

Laurent



  reply	other threads:[~2020-04-16 19:17 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-16 15:28 [PULL 0/1] Linux user for 5.0 patches Laurent Vivier
2020-04-16 15:28 ` [PULL 1/1] linux-user/syscall.c: add target-to-host mapping for epoll_create1() Laurent Vivier
2020-04-16 16:03 ` [PULL 0/1] Linux user for 5.0 patches Peter Maydell
2020-04-16 17:16   ` Laurent Vivier
2020-04-16 19:08     ` Peter Maydell
2020-04-16 19:15       ` Laurent Vivier [this message]
2020-04-20 18:55       ` Peter Maydell
  -- strict thread matches above, loose matches on Subject: below --
2020-03-30 10:29 Laurent Vivier
2020-03-30 11:32 ` no-reply
2020-03-30 12:14 ` 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=90666b58-6e4e-8f4a-c27a-eed2ce2a73a3@vivier.eu \
    --to=laurent@vivier.eu \
    --cc=peter.maydell@linaro.org \
    --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.