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 5E87BA0093; Tue, 7 Dec 2021 12:51:48 +0100 (CET) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id D7E3D41152; Tue, 7 Dec 2021 12:51:47 +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 3098C4114F for ; Tue, 7 Dec 2021 12:51:47 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1638877906; 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=JEqFcbOvjpiaiYFkobrDzYMkV4/xYH/kkL5k35VfUS4=; b=a5Yn1U+a2fckma84rFS8ZUA7a3dK5oBEKSk7PvX/9OrEwqK4ClcbHyjZHBkA72Yk/GBR0v y89oacop2dhMqibVtM45Tpf3OrtFRwxtrbgkooFhq9rkVUBfh4ok6+ysSuH+8OrN2zqs6S LYVMZhWmXqoX1m/MakNX/VpS07QorbM= Received: from mail-wm1-f71.google.com (mail-wm1-f71.google.com [209.85.128.71]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id us-mta-380-2KchUz6sOZmYifeQd9nqWw-1; Tue, 07 Dec 2021 06:51:44 -0500 X-MC-Unique: 2KchUz6sOZmYifeQd9nqWw-1 Received: by mail-wm1-f71.google.com with SMTP id n16-20020a05600c3b9000b003331973fdbbso1268448wms.0 for ; Tue, 07 Dec 2021 03:51:44 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:message-id:date:mime-version:user-agent :content-language:to:cc:references:from:subject:in-reply-to :content-transfer-encoding; bh=JEqFcbOvjpiaiYFkobrDzYMkV4/xYH/kkL5k35VfUS4=; b=rbrl+Wx1Lxs9RCHk3Jr1NhuohS4kNvEV8Lk8ZRktCjIFiOZr3STcAs3NS2zzoXOFo8 1x/Vv6Ps8DytQKuTg/vluJtP51AXphmBRC+VX/IfFD1UvmM1K+ewvWa/2JdCPmxYRujh fpzcB23mFzYkoi2GFQrMO96CnmYMyp5ekEBPMXPSSxTJuBSAwu/PPw/JMEsrU9D8pS72 7DMk9c7oN+Lvc7ZGwaM9bnnXfuR0bCCP456Z42WV05yWwD8GZ9l5XXzMyD26WpP6OihY qaWld1+wNgYgo5iiipHlf8J4dU92QotjSsEzZzg0FESYig6M1iODZW5jM2qyZ55N4+6T R0Hg== X-Gm-Message-State: AOAM531JI+BcURu+7kSVm7u/S7PsGHutVVyfGbyXOlERIPU7JqTsrQ2i JQzy6xZkPcgYu+grGKWp6fHAZEaKRMqhT22mI0joLvSQq60nb6+W6HQFN0xIfqzL4FRe/TEb5xO 8jMA= X-Received: by 2002:a05:600c:2195:: with SMTP id e21mr6460488wme.187.1638877903330; Tue, 07 Dec 2021 03:51:43 -0800 (PST) X-Google-Smtp-Source: ABdhPJw1xnkUK6/Sz9tcsvCgtzhLI6yUApqNkXYjJurcEZ+NOhVcfMbHCVcs32sGUuxXye8opqMHXw== X-Received: by 2002:a05:600c:2195:: with SMTP id e21mr6460452wme.187.1638877903094; Tue, 07 Dec 2021 03:51:43 -0800 (PST) Received: from [192.168.0.36] ([78.19.108.41]) by smtp.gmail.com with ESMTPSA id a10sm2353536wmq.27.2021.12.07.03.51.41 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Tue, 07 Dec 2021 03:51:42 -0800 (PST) Message-ID: <4ae78b06-5143-0304-b2c6-03dffaeb0401@redhat.com> Date: Tue, 7 Dec 2021 11:51:41 +0000 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Thunderbird/91.3.0 To: Ferruh Yigit , Thomas Monjalon , John McNamara , David Marchand Cc: Jerin Jacob , dpdk-dev , Akhil Goyal , Declan Doherty , Ruifeng Wang , Jan Viktorin , Bruce Richardson , Ray Kinsella , Radha Mohan Chintakuntla , Veerasenareddy Burru , Nithin Dabilpuram , Kiran Kumar K , Sunil Kumar Kori , Satha Rao , Nalla Pradeep , Ciara Power , Pavan Nikhilesh , Shijith Thotton , Ashwin Sekhar T K , Anatoly Burakov , Satananda Burla , Liron Himi , Jerin Jacob References: <20211206083542.3115019-1-jerinj@marvell.com> From: Kevin Traynor Subject: Re: [dpdk-dev] [PATCH v1] drivers: remove octeontx2 drivers In-Reply-To: Authentication-Results: relay.mimecast.com; auth=pass smtp.auth=CUSA124A263 smtp.mailfrom=ktraynor@redhat.com X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Language: en-US Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit 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 On 07/12/2021 11:01, Ferruh Yigit wrote: > On 12/7/2021 7:39 AM, Jerin Jacob wrote: >> On Mon, Dec 6, 2021 at 7:05 PM Ferruh Yigit wrote: >>> >>> On 12/6/2021 8:35 AM, jerinj@marvell.com wrote: >>>> From: Jerin Jacob >>>> >>>> As per the deprecation notice, In the view of enabling unified driver >>>> for octeontx2(cn9k)/octeontx3(cn10k), removing drivers/octeontx2 >>>> drivers and replace with drivers/cnxk/ which >>>> supports both octeontx2(cn9k) and octeontx3(cn10k) SoCs. >>>> >>>> This patch does the following >>>> >>>> - Replace drivers/common/octeontx2/ with drivers/common/cnxk/ >>>> - Replace drivers/mempool/octeontx2/ with drivers/mempool/cnxk/ >>>> - Replace drivers/net/octeontx2/ with drivers/net/cnxk/ >>>> - Replace drivers/event/octeontx2/ with drivers/event/cnxk/ >>>> - Replace drivers/crypto/octeontx2/ with drivers/crypto/cnxk/ >>>> - Rename config/arm/arm64_octeontx2_linux_gcc as >>>> config/arm/arm64_cn9k_linux_gcc >>>> - Update the documentation and MAINTAINERS to reflect the same. >>>> - Change the reference to OCTEONTX2 as OCTEON 9. The kernel related >>>> documentation is not accounted for this change as kernel documentation >>>> still uses OCTEONTX2. >>>> >>>> Depends-on: series-20804 ("common/cnxk: add REE HW definitions") >>>> Signed-off-by: Jerin Jacob >>>> --- >>>> MAINTAINERS | 37 - >>>> app/test/meson.build | 1 - >>>> app/test/test_cryptodev.c | 7 - >>>> app/test/test_cryptodev.h | 1 - >>>> app/test/test_cryptodev_asym.c | 17 - >>>> app/test/test_eventdev.c | 8 - >>>> config/arm/arm64_cn10k_linux_gcc | 1 - >>>> ...teontx2_linux_gcc => arm64_cn9k_linux_gcc} | 3 +- >>>> config/arm/meson.build | 10 +- >>>> devtools/check-abi.sh | 4 + >>>> doc/guides/cryptodevs/features/octeontx2.ini | 87 - >>>> doc/guides/cryptodevs/index.rst | 1 - >>>> doc/guides/cryptodevs/octeontx2.rst | 188 - >>>> doc/guides/dmadevs/cnxk.rst | 2 +- >>>> doc/guides/eventdevs/features/octeontx2.ini | 30 - >>>> doc/guides/eventdevs/index.rst | 1 - >>>> doc/guides/eventdevs/octeontx2.rst | 178 - >>>> doc/guides/mempool/index.rst | 1 - >>>> doc/guides/mempool/octeontx2.rst | 92 - >>>> doc/guides/nics/cnxk.rst | 4 +- >>>> doc/guides/nics/features/octeontx2.ini | 97 - >>>> doc/guides/nics/features/octeontx2_vec.ini | 48 - >>>> doc/guides/nics/features/octeontx2_vf.ini | 45 - >>>> doc/guides/nics/index.rst | 1 - >>>> doc/guides/nics/octeontx2.rst | 465 --- >>>> doc/guides/nics/octeontx_ep.rst | 4 +- >>>> doc/guides/platform/cnxk.rst | 12 + >>>> .../octeontx2_packet_flow_hw_accelerators.svg | 2804 -------------- >>>> .../img/octeontx2_resource_virtualization.svg | 2418 ------------ >>>> doc/guides/platform/index.rst | 1 - >>>> doc/guides/platform/octeontx2.rst | 520 --- >>>> doc/guides/rel_notes/deprecation.rst | 17 - >>>> doc/guides/rel_notes/release_19_08.rst | 12 +- >>>> doc/guides/rel_notes/release_19_11.rst | 6 +- >>>> doc/guides/rel_notes/release_20_02.rst | 8 +- >>>> doc/guides/rel_notes/release_20_05.rst | 4 +- >>>> doc/guides/rel_notes/release_20_08.rst | 6 +- >>>> doc/guides/rel_notes/release_20_11.rst | 8 +- >>>> doc/guides/rel_notes/release_21_02.rst | 10 +- >>>> doc/guides/rel_notes/release_21_05.rst | 6 +- >>>> doc/guides/rel_notes/release_21_11.rst | 2 +- >>> >>> Not sure about updating old release notes files, using 'octeontx2' still can make >>> sense for the context of those releases. >> >> OK. I will send v2 with keeping octeontx2 in OLD release notes. >> >> > > Not related with this set specifically, a more general question about updating > old release notes. > For me release notes should be frozen with the release and shouldn't be updated > at all afterwards, but there is no agreement on this and in practice old release > notes are updated. > > My question is, is there any benefit to keep a separate release notes file for > each release, and need to maintain old ones. > What about having a single release file, 'release.rst', and reset it after each > release? > I think there is a benefit to keeping them all - you can quickly look/grep through the files for multiple releases. e.g. if you wanted to check when a driver/feature was added etc. I agree it doesn't make sense to update them, unless there was a mistake at the time of release.