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 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 smtp.lore.kernel.org (Postfix) with ESMTPS id 1DEBBC433EF for ; Tue, 19 Jul 2022 14:44:19 +0000 (UTC) Received: from localhost ([::1]:52026 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1oDoSQ-0007ww-0O for qemu-devel@archiver.kernel.org; Tue, 19 Jul 2022 10:44:18 -0400 Received: from eggs.gnu.org ([2001:470:142:3::10]:59512) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1oDoDP-0008A2-3D for qemu-devel@nongnu.org; Tue, 19 Jul 2022 10:28:48 -0400 Received: from us-smtp-delivery-124.mimecast.com ([170.10.133.124]:32052) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1oDoDM-0000zg-9f for qemu-devel@nongnu.org; Tue, 19 Jul 2022 10:28:45 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1658240923; h=from:from:reply-to:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:cc:mime-version:mime-version: content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=KQbxbMX82IhG6NuHRrBOUB3ubO/WTus8HJaAK9JujsQ=; b=WkJPP3nhcLLtCsoNwJIqpexscJjM6QpWoNYkdaJnaLdjh7M4PmQHMBD8lOKJU9GscT+T4h lAAA+YRqIoSVJdCKS3JBnIKaPcpzltg6AlcsnS1BnmII8YOw5h8NN7zoQ09nG5JgttBJ5Y 6wRZqkXLu6gzMjn+dRyFqaao4aHwNbs= Received: from mimecast-mx02.redhat.com (mx3-rdu2.redhat.com [66.187.233.73]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id us-mta-456-9PCnLMsAORC2Cd6m2YEvEA-1; Tue, 19 Jul 2022 10:28:36 -0400 X-MC-Unique: 9PCnLMsAORC2Cd6m2YEvEA-1 Received: from smtp.corp.redhat.com (int-mx06.intmail.prod.int.rdu2.redhat.com [10.11.54.6]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx02.redhat.com (Postfix) with ESMTPS id B755629AA3BC; Tue, 19 Jul 2022 14:28:35 +0000 (UTC) Received: from redhat.com (unknown [10.33.36.156]) by smtp.corp.redhat.com (Postfix) with ESMTPS id 0C0FF2166B29; Tue, 19 Jul 2022 14:28:33 +0000 (UTC) Date: Tue, 19 Jul 2022 15:28:31 +0100 From: Daniel =?utf-8?B?UC4gQmVycmFuZ8Op?= To: Cindy Lu Cc: mst@redhat.com, jasowang@redhat.com, kraxel@redhat.com, dgilbert@redhat.com, stefanha@redhat.com, arei.gonglei@huawei.com, marcandre.lureau@redhat.com, qemu-devel@nongnu.org Subject: Re: [PATCH v12 00/10] vhost-vdpa: add support for configure interrupt Message-ID: References: <20220719134655.522538-1-lulu@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <20220719134655.522538-1-lulu@redhat.com> User-Agent: Mutt/2.2.6 (2022-06-05) X-Scanned-By: MIMEDefang 2.78 on 10.11.54.6 Received-SPF: pass client-ip=170.10.133.124; envelope-from=berrange@redhat.com; helo=us-smtp-delivery-124.mimecast.com X-Spam_score_int: -21 X-Spam_score: -2.2 X-Spam_bar: -- X-Spam_report: (-2.2 / 5.0 requ) BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.082, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01 autolearn=ham autolearn_force=no X-Spam_action: no action X-BeenThere: qemu-devel@nongnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Reply-To: Daniel =?utf-8?B?UC4gQmVycmFuZ8Op?= Errors-To: qemu-devel-bounces+qemu-devel=archiver.kernel.org@nongnu.org Sender: "Qemu-devel" On Tue, Jul 19, 2022 at 09:46:45PM +0800, Cindy Lu wrote: > These patches introduced the support for configure interrupt  The email threading of this series isn't setup right. Each patch is appearing as a new top level mail, rather than as a reply to the cover letter. I can encourage using 'git-publish' to send patch series to qemu-devel to avoid this kind of mistake, as well as giving tracking of each version you send through local git tags, and being able to auto-remember the cover letter contents. With regards, Daniel [1] https://github.com/stefanha/git-publish -- |: https://berrange.com -o- https://www.flickr.com/photos/dberrange :| |: https://libvirt.org -o- https://fstop138.berrange.com :| |: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|