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 6E28F45E1A; Thu, 5 Dec 2024 09:04:42 +0100 (CET) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id F2486402C4; Thu, 5 Dec 2024 09:04:41 +0100 (CET) Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.133.124]) by mails.dpdk.org (Postfix) with ESMTP id 3D1BE402AE for ; Thu, 5 Dec 2024 09:04:41 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1733385880; 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=x75yrANZLcRr5KTU+zGT/7pJUR38kSoNbiUAiZsdKew=; b=dGSaozWZE4k8FBGEyRbgbzknQwY7cIb3CdMhEAUTDZoFH/t0WZsvKcU7H21K3mIzKz9n8K ewb4T+e0Syw2EcveHA6XG9yoBPbHLk3r74eDGImaWYmKLagCmgKlDanKZh10YxvpqWvMXB w05jUhGWl93zCLM1pkl5A4SRcTrHx3c= Received: from mail-pj1-f71.google.com (mail-pj1-f71.google.com [209.85.216.71]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.3, cipher=TLS_AES_256_GCM_SHA384) id us-mta-638-Jz2GtAzDPGOk_kkdjzayew-1; Thu, 05 Dec 2024 03:04:39 -0500 X-MC-Unique: Jz2GtAzDPGOk_kkdjzayew-1 X-Mimecast-MFC-AGG-ID: Jz2GtAzDPGOk_kkdjzayew Received: by mail-pj1-f71.google.com with SMTP id 98e67ed59e1d1-2ee36569f4cso833551a91.2 for ; Thu, 05 Dec 2024 00:04:39 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1733385878; x=1733990678; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=x75yrANZLcRr5KTU+zGT/7pJUR38kSoNbiUAiZsdKew=; b=kaS0sI45baFW74HUTr+BvG8AdFmWqrjFPSsMIJZQ0CrX8MnQY9vo1V5Tf4JxITDN27 /XgGjBmvUbTuJN22CtNWzjzgd7N/69bZ8IKBsGr2q4XNpSeKS/twZ0o+m89MP64wMP49 QY8R8TpedrMwG7OmdqOqTEhJJip++UO5dd2xnlrWbfdMNcq9BJx+xjDDBPbxlyFJ5IDE qJnFfHqrBysXmMjDrJ9su8Q9V24TGfIRB6dZwymjL6kzmUrw8JVOULs7utHdA0Osb0zR z9Q4Pq4p5EArNmLgqcTAu4DnX1LUX5oygIAY2l634zsp08TPWH9SN7F9mP1uFpB/RBvR N/oA== X-Gm-Message-State: AOJu0Yzxfy/FwbwpmIxhs1X2OcioCwSpnNE79jPiXXViqFjUcEDKbqn1 bx2s3BxayFiXgl3KqTqVl2AVyg2H0KnHbHMAZrAgDxOplySMexXCUYhIG/VV4jEY/5Wbw0agXQh Y+T5IWY/+hbDQ7TyLcwQbzdDPSm1NjU3WeHd9hNdl0UPA8LXbYxtAbmqfirauwQgClLDL1pVDLK JOlu5Mg6AFlwwiA1w= X-Gm-Gg: ASbGncucGRjtOy3MnMvwDKO2UdXoG07l+78s+TFBrOq3bqT7KxrZXG1voFSdWtO6v5u L6oftickOFEUkuXSqwvN0nj/E+oQsNWWVFbxN+g== X-Received: by 2002:a17:90b:1c09:b0:2ea:61de:38f7 with SMTP id 98e67ed59e1d1-2ef0124eedcmr12190586a91.29.1733385878532; Thu, 05 Dec 2024 00:04:38 -0800 (PST) X-Google-Smtp-Source: AGHT+IE2jN9oyXEPsGhwrdECEs92LjuQj9abm7ju3LI0bf4CvE4ecJRjnFB0dUPyL8D78Qqa/b2UWPyDBRCfnuiCKTs= X-Received: by 2002:a17:90b:1c09:b0:2ea:61de:38f7 with SMTP id 98e67ed59e1d1-2ef0124eedcmr12190561a91.29.1733385878133; Thu, 05 Dec 2024 00:04:38 -0800 (PST) MIME-Version: 1.0 References: <20241113023323.3228516-12-li.hanxiao@zte.com.cn> <20241204013355.389043-1-li.hanxiao@zte.com.cn> In-Reply-To: <20241204013355.389043-1-li.hanxiao@zte.com.cn> From: David Marchand Date: Thu, 5 Dec 2024 09:04:25 +0100 Message-ID: Subject: Re: [v22,13/13] compress/zsda: add zsda compressdev capabilities To: Hanxiao Li Cc: dev@dpdk.org, gakhil@marvell.com X-Mimecast-Spam-Score: 0 X-Mimecast-MFC-PROC-ID: Ypo81wWgk5qy68ybYEyQ-MaSEKnhr628-wxC9GwEqZk_1733385878 X-Mimecast-Originator: redhat.com Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable 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 Hello Hanxiao, My two cents. On Wed, Dec 4, 2024 at 2:41=E2=80=AFAM Hanxiao Li w= rote: > > Hi akhil: > > I noticed that DPDK24.11 has been released and state of the my patches ha= s been changed to "New" from "Defer". > > And I have some questions about how to proceed with submitting patches. > > 1. In the last version, I have submitted to v22. If I want to continue= submitting, should I submit to v23 or v1? It would be confusing to have multiple patches on the mailing list with the same numbering. The more recent patches have already gone through a number of reviews and changes, and the numbering helps tracking this down. So please keep on increasing the revision number when submitting new series= . > > 2. Should I submit patches based on the latest version as soon as poss= ible, or wait for your comments before submitting? > > 3. I think I need to add something to the release_25_03.rst. But I did= not find the file in code. > So, what should I do? > Don=E9=88=A5=E6=AA=9B write this document for now, and add it after i= t is released later? > Or should I wait until this file exists before submitting? We merged the rc0 patch yesterday. Once Akhil rebases next-crypto, the new RN file will be present. --=20 David Marchand