From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from dpdk.org (dpdk.org [92.243.14.124]) by inbox.dpdk.org (Postfix) with ESMTP id BBF65A0567 for ; Tue, 10 Mar 2020 15:09:28 +0100 (CET) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id AB6711BFFA; Tue, 10 Mar 2020 15:09:28 +0100 (CET) Received: from us-smtp-delivery-1.mimecast.com (us-smtp-2.mimecast.com [207.211.31.81]) by dpdk.org (Postfix) with ESMTP id 0362F2BE6 for ; Tue, 10 Mar 2020 15:09:26 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1583849366; h=from:from: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=E+a3aofpfCa3+nclqp7L6bJP2BlJAE5OjbZKnGGOATM=; b=bWphsYWZsfGvUAosuuDz6kdfAV7inMHQRUUjKZ3XCyViMKoR5qNU8VLKceg3Y1I8ZuWJSO hfjM+CclFMIYH7teotqBR+iukBpyghEGU7xIcl90RdOMqjsL3XSWHQvdDaJIkUowTntYa0 2V9GU7u7Nd3Z6ItMzNzsBPHn/47i5rQ= Received: from mimecast-mx01.redhat.com (mimecast-mx01.redhat.com [209.132.183.4]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-171-KiXg0CGBMoyv21PBL87JRA-1; Tue, 10 Mar 2020 10:09:22 -0400 X-MC-Unique: KiXg0CGBMoyv21PBL87JRA-1 Received: from smtp.corp.redhat.com (int-mx06.intmail.prod.int.phx2.redhat.com [10.5.11.16]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx01.redhat.com (Postfix) with ESMTPS id DBC87107B285; Tue, 10 Mar 2020 14:09:20 +0000 (UTC) Received: from dhcp-25.97.bos.redhat.com (unknown [10.18.25.84]) by smtp.corp.redhat.com (Postfix) with ESMTPS id EE1BA5C28D; Tue, 10 Mar 2020 14:09:16 +0000 (UTC) From: Aaron Conole To: David Marchand Cc: Haiyue Wang , dev , Xiaolong Ye , Qi Zhang , Qiming Yang , Beilei Xing , Wei Zhao , ci@dpdk.org References: <20200309141437.11800-1-haiyue.wang@intel.com> Date: Tue, 10 Mar 2020 10:09:16 -0400 In-Reply-To: (David Marchand's message of "Mon, 9 Mar 2020 16:36:54 +0100") Message-ID: User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/26.3 (gnu/linux) MIME-Version: 1.0 X-Scanned-By: MIMEDefang 2.79 on 10.5.11.16 X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Type: text/plain Content-Transfer-Encoding: quoted-printable Subject: Re: [dpdk-ci] [dpdk-dev] [PATCH v1 0/4] add Intel DCF PMD support X-BeenThere: ci@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK CI discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: ci-bounces@dpdk.org Sender: "ci" David Marchand writes: > On Mon, Mar 9, 2020 at 3:22 PM Haiyue Wang wrote: >> >> A DCF (Device Config Function) based approach is proposed where a device >> bound to the device's VF0 can act as a sole controlling entity to exerci= se >> advance functionality (such as switch, ACL) for rest of the VFs. >> >> The DCF works as a standalone PMD to support this function, which shares= the >> ice PMD flow control core function and the iavf virtchnl mailbox core mo= dule. >> >> This patchset is based on: >> [1] https://patchwork.dpdk.org/cover/66417/ update ice base code > > The problem is that the CI(s) won't handle this. > Example for the robot: https://travis-ci.com/ovsrobot/dpdk/builds/1524619= 07 > > Maybe we could add something as an annotation to the cover letter or > the first patch of a series so that the CI(s) can detect and try to be > intelligent? It's something that's possibly worth doing; I can update the bot to recognize: series_XXX in the cover-letter metadata (IE: between the '[...]'), and automatically check out the correct branch. Additionally, if the idea is not to get the patch applied right away while finalizing on the preceding series, the RFC keyword will prevent the bot from running. THAT SAID In general, I dislike posting series that depend on other series. It makes review much harder, and if there's a feedback on the preceding series that requires lots of change, the dependent series may also need to be re-done completely. I see there are more replies to this thread - sorry I didn't get to it yesterday (personal stuff).