From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by inbox.dpdk.org (Postfix) with ESMTP id C0EB045626; Tue, 16 Jul 2024 04:39:02 +0200 (CEST) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id A68CB40E32; Tue, 16 Jul 2024 04:39:02 +0200 (CEST) Received: from mail.loongson.cn (mail.loongson.cn [114.242.206.163]) by mails.dpdk.org (Postfix) with ESMTP id F17E8402B0 for ; Tue, 16 Jul 2024 04:38:43 +0200 (CEST) Received: from loongson.cn (unknown [10.20.42.74]) by gateway (Coremail) with SMTP id _____8BxVuoy3ZVm+9kEAA--.3563S3; Tue, 16 Jul 2024 10:38:42 +0800 (CST) Received: from [10.20.42.74] (unknown [10.20.42.74]) by localhost.localdomain (Coremail) with SMTP id AQAAf8AxQcQu3ZVm0KdKAA--.570S3; Tue, 16 Jul 2024 10:38:40 +0800 (CST) Subject: Re: [PATCH v7 01/21] net/ntnic: add ethdev and makes PMD available To: Patrick Robb Cc: dev@dpdk.org, mko-plv@napatech.com, ckm@napatech.com, andrew.rybchenko@oktetlabs.ru, ferruh.yigit@amd.com, Thomas Monjalon , Serhii Iliushyk References: <20240530144929.4127931-1-sil-plv@napatech.com> <20240712094831.861260-1-sil-plv@napatech.com> <9a9380f2-4136-bfae-9f28-518d28ed3c34@loongson.cn> From: zhoumin Message-ID: <08536ed9-b4ce-9385-3e76-62fcb0e686ee@loongson.cn> Date: Tue, 16 Jul 2024 02:36:54 +0000 User-Agent: Mozilla/5.0 (X11; Linux loongarch64; rv:68.0) Gecko/20100101 Thunderbird/68.7.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Content-Language: en-US X-CM-TRANSID: AQAAf8AxQcQu3ZVm0KdKAA--.570S3 X-CM-SenderInfo: 52kr3ztlq6z05rqj20fqof0/1tbiAQAAAWaV0hgAqQAEsU X-Coremail-Antispam: 1Uk129KBj93XoWxGry3Zr4DKF4UArW5uFW7GFX_yoW5Arykpr 9xt3W3Krn3tr97Ka1Fyw1xuF1Fvr4kGF4Dur1rCrWq9FyDXFyruFnFqFyrAry8uwn5tw13 Xrs8ta4xWF1UuagCm3ZEXasCq-sJn29KB7ZKAUJUUUUU529EdanIXcx71UUUUU7KY7ZEXa sCq-sGcSsGvfJ3Ic02F40EFcxC0VAKzVAqx4xG6I80ebIjqfuFe4nvWSU5nxnvy29KBjDU 0xBIdaVrnRJUUUvFb4IE77IF4wAFF20E14v26r1j6r4UM7CY07I20VC2zVCF04k26cxKx2 IYs7xG6rWj6s0DM7CIcVAFz4kK6r106r15M28lY4IEw2IIxxk0rwA2F7IY1VAKz4vEj48v e4kI8wA2z4x0Y4vE2Ix0cI8IcVAFwI0_JFI_Gr1l84ACjcxK6xIIjxv20xvEc7CjxVAFwI 0_Jr0_Gr1l84ACjcxK6I8E87Iv67AKxVWxJVW8Jr1l84ACjcxK6I8E87Iv6xkF7I0E14v2 6r4UJVWxJr1le2I262IYc4CY6c8Ij28IcVAaY2xG8wAqjxCEc2xF0cIa020Ex4CE44I27w Aqx4xG64xvF2IEw4CE5I8CrVC2j2WlYx0E2Ix0cI8IcVAFwI0_JrI_JrylYx0Ex4A2jsIE 14v26r1j6r4UMcvjeVCFs4IE7xkEbVWUJVW8JwACjcxG0xvEwIxGrwCYjI0SjxkI62AI1c AE67vIY487MxAIw28IcxkI7VAKI48JMxC20s026xCaFVCjc4AY6r1j6r4UMI8I3I0E5I8C rVAFwI0_Jr0_Jr4lx2IqxVCjr7xvwVAFwI0_JrI_JrWlx4CE17CEb7AF67AKxVWUtVW8Zw CIc40Y0x0EwIxGrwCI42IY6xIIjxv20xvE14v26r1j6r1xMIIF0xvE2Ix0cI8IcVCY1x02 67AKxVWUJVW8JwCI42IY6xAIw20EY4v20xvaj40_Jr0_JF4lIxAIcVC2z280aVAFwI0_Jr 0_Gr1lIxAIcVC2z280aVCY1x0267AKxVWUJVW8JbIYCTnIWIevJa73UjIFyTuYvjxUzZ2- UUUUU X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Hi Patrick, Thanks for giving the link of commit `a6c3ec342ee1`. However I cannot checkout this commit in the next-net repository because the commit ID is not exist in the history of next-net repository. Could you find it? It seems that the commit `a6c3ec342ee1` is nearly identical to the commit `62edcfd6ea3c` except the minor change in the subjects as following: https://git.dpdk.org/next/dpdk-next-net/commit/?id=62edcfd6ea3c61639df68e4a315046d09f462e8c I'm able to checkout the commit `62edcfd6ea3c` in the next-net repository but fail to apply this series, because this series conflicts with the commit `a40ac9bcd85c`. Despite all this, I can apply this series successfully on the artifact of commit `a6c3ec342ee1`: https://git.dpdk.org/next/dpdk-next-net/snapshot/dpdk-next-net-a6c3ec342ee105e322ffdb21e810cdfd38455c62.zip Loongson lab always tries to update the local repository with the upstream before testing the series, and just applies the downloaded series to the local repository. So it's possible to skip some commits in Loongson lab when chooses the base for applying. Best regards, Min Zhou On Mon, Jul, 15, 2024 at 3:39PM, Patrick Robb wrote: > Hi Min Zhou, > > I am seeing that commit for next-net: > https://git.dpdk.org/next/dpdk-next-net/commit/?id=a6c3ec342ee105e322ffdb21e810cdfd38455c62 > > If you try to manually apply it on next-net, does it work? > > Pasting the logs from our apply process below for context: > > ``` > > Trying to checkout branch: origin/next-net-for-main > Checked out to next-net-for-main (a6c3ec342ee105e322ffdb21e810cdfd38455c62) > Applying patch... > > Applying: net/ntnic: add ethdev and makes PMD available > Applying: net/ntnic: add logging implementation > Applying: net/ntnic: add minimal initialization for PCI device > Applying: net/ntnic: add NT utilities implementation > Applying: net/ntnic: add VFIO module > Applying: net/ntnic: add basic eth dev ops to ntnic > Applying: net/ntnic: add core platform structures > Applying: net/ntnic: add adapter initialization > Applying: net/ntnic: add registers and FPGA model for NapaTech NIC > Applying: net/ntnic: add FPGA modules for initialization > Applying: net/ntnic: add FPGA initialization functionality > Applying: net/ntnic: add support of the NT200A0X smartNIC > Applying: net/ntnic: add startup and reset sequence for NT200A0X > Applying: net/ntnic: add clock profile for the NT200A0X smartNIC > Applying: net/ntnic: add link management skeleton > Applying: net/ntnic: add link 100G module ops > Applying: net/ntnic: add generic NIM and I2C modules > Applying: net/ntnic: add QSFP support > Applying: net/ntnic: add QSFP28 support > Applying: net/ntnic: add GPIO communication for NIMs > Applying: net/ntnic: add physical layer control module > > > Running test build... > The Meson build system > > ```