From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:46467) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1eIep2-00088M-QD for qemu-devel@nongnu.org; Sat, 25 Nov 2017 13:05:02 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1eIep1-0008Nk-Jf for qemu-devel@nongnu.org; Sat, 25 Nov 2017 13:05:00 -0500 Received: from mail-oi0-x22e.google.com ([2607:f8b0:4003:c06::22e]:38456) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1eIep1-0008NN-Df for qemu-devel@nongnu.org; Sat, 25 Nov 2017 13:04:59 -0500 Received: by mail-oi0-x22e.google.com with SMTP id g139so6954135oic.5 for ; Sat, 25 Nov 2017 10:04:59 -0800 (PST) MIME-Version: 1.0 In-Reply-To: References: From: Peter Maydell Date: Sat, 25 Nov 2017 18:04:37 +0000 Message-ID: Content-Type: text/plain; charset="UTF-8" Subject: Re: [Qemu-devel] [PATCH] BCM2837 and machine raspi3 List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: bzt bzt Cc: Andrew Baumann , "qemu-devel@nongnu.org" , "qemu-arm@nongnu.org" On 25 November 2017 at 16:43, bzt bzt wrote: > Dear Andrew, > > A month passed, and the maintainers didn't gave a damn about raspi3 support > in qemu. Any ideas? Sorry this patch fell through the cracks, but it looked to me to be in the state "patch got code review comments, waiting for submitter to resend a new version" (from about the point Konrad said "split this up, it's too big", which I agree with.) QEMU gets a lot of patches every day, so our code process relies on the submitter to prod things if what they're interested in seems to have been accidentally ignored: https://wiki.qemu.org/Contribute/SubmitAPatch#If_your_patch_seems_to_have_been_ignored FWIW, as far as I'm concerned Andrew pretty much is the maintainer as far as the raspi boards are concerned, so as far as those bits of code goes I'm happy to take his opinion on it. PS: if you send a new patch, send it as a new top level thread -- if you send it as a reply/followup to the first patch it's liable to not be noticed. thanks -- PMM