From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-2.2 required=3.0 tests=HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS,USER_AGENT_SANE_1 autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 7DA41C432C0 for ; Tue, 3 Dec 2019 06:53:06 +0000 (UTC) Received: from lists.gnu.org (lists.gnu.org [209.51.188.17]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPS id 552D2206E0 for ; Tue, 3 Dec 2019 06:53:06 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 552D2206E0 Authentication-Results: mail.kernel.org; dmarc=fail (p=none dis=none) header.from=intel.com Authentication-Results: mail.kernel.org; spf=pass smtp.mailfrom=qemu-devel-bounces+qemu-devel=archiver.kernel.org@nongnu.org Received: from localhost ([::1]:49242 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1ic23V-0007bT-CM for qemu-devel@archiver.kernel.org; Tue, 03 Dec 2019 01:53:05 -0500 Received: from eggs.gnu.org ([2001:470:142:3::10]:36986) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1ic21t-0006xv-TD for qemu-devel@nongnu.org; Tue, 03 Dec 2019 01:51:27 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ic21p-0005mS-IZ for qemu-devel@nongnu.org; Tue, 03 Dec 2019 01:51:23 -0500 Received: from mga12.intel.com ([192.55.52.136]:36020) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1ic21n-0005aN-KV for qemu-devel@nongnu.org; Tue, 03 Dec 2019 01:51:19 -0500 X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from orsmga005.jf.intel.com ([10.7.209.41]) by fmsmga106.fm.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 02 Dec 2019 22:51:09 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.69,272,1571727600"; d="scan'208";a="385195873" Received: from txu2-mobl.ccr.corp.intel.com (HELO [10.239.197.115]) ([10.239.197.115]) by orsmga005.jf.intel.com with ESMTP; 02 Dec 2019 22:51:07 -0800 Subject: Re: [PATCH v20 0/8] Build ACPI Heterogeneous Memory Attribute Table (HMAT) To: "Michael S. Tsirkin" , Markus Armbruster References: <20191129075634.682-1-tao3.xu@intel.com> <20191203003445-mutt-send-email-mst@kernel.org> <87y2vu7xt6.fsf@dusky.pond.sub.org> <20191203010755-mutt-send-email-mst@kernel.org> From: Tao Xu Message-ID: Date: Tue, 3 Dec 2019 14:51:06 +0800 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.9.1 MIME-Version: 1.0 In-Reply-To: <20191203010755-mutt-send-email-mst@kernel.org> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-detected-operating-system: by eggs.gnu.org: Genre and OS details not recognized. X-Received-From: 192.55.52.136 X-BeenThere: qemu-devel@nongnu.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: "lvivier@redhat.com" , "thuth@redhat.com" , "ehabkost@redhat.com" , "sw@weilnetz.de" , "Du, Fan" , "qemu-devel@nongnu.org" , "mdroth@linux.vnet.ibm.com" , "jonathan.cameron@huawei.com" , "imammedo@redhat.com" , "Liu, Jingqi" Errors-To: qemu-devel-bounces+qemu-devel=archiver.kernel.org@nongnu.org Sender: "Qemu-devel" On 12/3/2019 2:25 PM, Michael S. Tsirkin wrote: > On Tue, Dec 03, 2019 at 07:00:53AM +0100, Markus Armbruster wrote: >> "Michael S. Tsirkin" writes: >> >>> On Tue, Dec 03, 2019 at 08:53:30AM +0800, Tao Xu wrote: >>>> Hi Michael, >>>> >>>> Could this patch series be queued? >>>> Thank you very much! >>>> >>>> Tao >>> >>> QEMU is in freeze, so not yet. Please ping after the release. >> >> Just to avoid confusion: it's Michael's personal preference not to >> process patches for the next version during freeze. Other maintainers >> do, and that's actually the project's policy: >> >> Subject: QEMU Summit 2017: minutes >> Message-ID: >> https://lists.nongnu.org/archive/html/qemu-devel/2017-11/msg04453.html >> >> qemu-next: >> * Problem 1: Contributors cannot get patches merged during freeze >> (bad experience) >> [...] >> * Markus Armbruster: Problem 1 is solved if maintainers keep their own >> -next trees >> * Paolo Bonzini: Maintaining -next could slow down or create work for >> -freeze (e.g. who does backports) >> * Action: Maintainers mustn't tell submitters to go away just because >> we're in a release freeze (it's up to them whether they prefer to >> maintain a "-next" tree for their subsystem with patches queued for >> the following release, or track which patches they've accepted >> some other way) >> * We're not going to have an official project-wide "-next" tree, though >> >> Michael, would queuing up patches in a -next branch really be too much >> trouble for you? > > Thanks for pointing this out! > > I stopped asking for re-post since awhile ago. I don't queue patches in > a public tree but I do review and do keep track of pending patches. > > I tend to ask contributors to also ping because sometimes there's a > problem with rebase, I drop the patch but forget to tell the > contributor, and it tends to happen more with big patchsets posted during > freeze as there's a rush to merge changes right after that. > I usually don't bother people with this for small patches though. > > I'll try to be clearer in my communication so contributors don't feel > stressed. > > Would something like: > > "I'll queue it for merge after the release. If possible please ping me > after the release to help make sure it didn't get dropped." > > be clearer? > > Hopefully windows CI efforts will soon bear fruit to the point where > they stress PCI enough to make maintaining next worth the effort. > I see. Thanks for Markus and Michael's kindly response. I feel happy rather than stressed in QEMU community :)