From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:45692) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1fIay8-0006aD-Tj for qemu-devel@nongnu.org; Tue, 15 May 2018 10:30:29 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1fIay2-00068e-VY for qemu-devel@nongnu.org; Tue, 15 May 2018 10:30:24 -0400 Received: from mx3-rdu2.redhat.com ([66.187.233.73]:33968 helo=mx1.redhat.com) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1fIay2-00068H-Jz for qemu-devel@nongnu.org; Tue, 15 May 2018 10:30:18 -0400 References: <20180313044944.21058-1-aik@ozlabs.ru> <20180313074442.xw5deum6xfw5tvjw@var.youpi.perso.aquilenet.fr> <87d13bdd-4a33-fb05-0c7c-36aabbd3d038@ozlabs.ru> From: Eric Blake Message-ID: Date: Tue, 15 May 2018 09:30:17 -0500 MIME-Version: 1.0 In-Reply-To: <87d13bdd-4a33-fb05-0c7c-36aabbd3d038@ozlabs.ru> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] [PATCH qemu v2] slirp/debug: Print IP addresses in human readable form List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Alexey Kardashevskiy , Samuel Thibault Cc: qemu-devel@nongnu.org On 05/14/2018 02:00 AM, Alexey Kardashevskiy wrote: > On 13/3/18 6:44 pm, Samuel Thibault wrote: >> Alexey Kardashevskiy, on mar. 13 mars 2018 15:49:44 +1100, wrote: >>> Signed-off-by: Alexey Kardashevskiy >> >> Applied to my tree, thanks! > > > And what is your tree, is this something to be merged sometime later > somewhere? :) Per MAINTAINERS: SLIRP M: Samuel Thibault M: Jan Kiszka S: Maintained F: slirp/ F: net/slirp.c F: include/net/slirp.h T: git git://git.kiszka.org/qemu.git queues/slirp which shows Jan's staging tree, but not Samuel's. It's not a requirement for a maintainer to have a public-facing staging tree, but many of them do, as it gives you a chance to test that what will later be in a pull request matches what you expect. At any rate, https://wiki.qemu.org/Contribute/SubmitAPatch#Is_my_patch_in.3F mentions that maintainers will batch together various related patches and send a pull request for inclusion in the main repository, thus even when a patch has been reviewed and staged, it may be another week or two before it lands in mainline. Yes, it can feel slow, but in general it works out for the best (as we have more chances to flag potential problems before they affect everyone by being in mainline). -- Eric Blake, Principal Software Engineer Red Hat, Inc. +1-919-301-3266 Virtualization: qemu.org | libvirt.org