get:
Show a patch.

patch:
Update a patch.

put:
Update a patch.

GET /api/patches/139011/?format=api
HTTP 200 OK
Allow: GET, PUT, PATCH, HEAD, OPTIONS
Content-Type: application/json
Vary: Accept

{
    "id": 139011,
    "url": "http://patches.dpdk.org/api/patches/139011/?format=api",
    "web_url": "http://patches.dpdk.org/project/dpdk/patch/20240330175437.2169948-1-david.marchand@redhat.com/",
    "project": {
        "id": 1,
        "url": "http://patches.dpdk.org/api/projects/1/?format=api",
        "name": "DPDK",
        "link_name": "dpdk",
        "list_id": "dev.dpdk.org",
        "list_email": "dev@dpdk.org",
        "web_url": "http://core.dpdk.org",
        "scm_url": "git://dpdk.org/dpdk",
        "webscm_url": "http://git.dpdk.org/dpdk",
        "list_archive_url": "https://inbox.dpdk.org/dev",
        "list_archive_url_format": "https://inbox.dpdk.org/dev/{}",
        "commit_url_format": ""
    },
    "msgid": "<20240330175437.2169948-1-david.marchand@redhat.com>",
    "list_archive_url": "https://inbox.dpdk.org/dev/20240330175437.2169948-1-david.marchand@redhat.com",
    "date": "2024-03-30T17:54:37",
    "name": "version: 24.07-rc0",
    "commit_ref": null,
    "pull_url": null,
    "state": "accepted",
    "archived": false,
    "hash": "63afe2daec6f7970e468d7494345c469a991b46d",
    "submitter": {
        "id": 1173,
        "url": "http://patches.dpdk.org/api/people/1173/?format=api",
        "name": "David Marchand",
        "email": "david.marchand@redhat.com"
    },
    "delegate": {
        "id": 24651,
        "url": "http://patches.dpdk.org/api/users/24651/?format=api",
        "username": "dmarchand",
        "first_name": "David",
        "last_name": "Marchand",
        "email": "david.marchand@redhat.com"
    },
    "mbox": "http://patches.dpdk.org/project/dpdk/patch/20240330175437.2169948-1-david.marchand@redhat.com/mbox/",
    "series": [
        {
            "id": 31650,
            "url": "http://patches.dpdk.org/api/series/31650/?format=api",
            "web_url": "http://patches.dpdk.org/project/dpdk/list/?series=31650",
            "date": "2024-03-30T17:54:37",
            "name": "version: 24.07-rc0",
            "version": 1,
            "mbox": "http://patches.dpdk.org/series/31650/mbox/"
        }
    ],
    "comments": "http://patches.dpdk.org/api/patches/139011/comments/",
    "check": "warning",
    "checks": "http://patches.dpdk.org/api/patches/139011/checks/",
    "tags": {},
    "related": [],
    "headers": {
        "Return-Path": "<dev-bounces@dpdk.org>",
        "X-Original-To": "patchwork@inbox.dpdk.org",
        "Delivered-To": "patchwork@inbox.dpdk.org",
        "Received": [
            "from mails.dpdk.org (mails.dpdk.org [217.70.189.124])\n\tby inbox.dpdk.org (Postfix) with ESMTP id F25DE43D87;\n\tSat, 30 Mar 2024 18:55:07 +0100 (CET)",
            "from mails.dpdk.org (localhost [127.0.0.1])\n\tby mails.dpdk.org (Postfix) with ESMTP id EBB0C402EC;\n\tSat, 30 Mar 2024 18:55:06 +0100 (CET)",
            "from us-smtp-delivery-124.mimecast.com\n (us-smtp-delivery-124.mimecast.com [170.10.133.124])\n by mails.dpdk.org (Postfix) with ESMTP id EE07C4021D\n for <dev@dpdk.org>; Sat, 30 Mar 2024 18:54:49 +0100 (CET)",
            "from mimecast-mx02.redhat.com (mx-ext.redhat.com [66.187.233.73])\n by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.3,\n cipher=TLS_AES_256_GCM_SHA384) id us-mta-458-pkHyIfPfPQid9aOFte1PeA-1; Sat,\n 30 Mar 2024 13:54:45 -0400",
            "from smtp.corp.redhat.com (int-mx04.intmail.prod.int.rdu2.redhat.com\n [10.11.54.4])\n (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)\n key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest\n SHA256)\n (No client certificate requested)\n by mimecast-mx02.redhat.com (Postfix) with ESMTPS id 7BA091C031C0;\n Sat, 30 Mar 2024 17:54:45 +0000 (UTC)",
            "from dmarchan.redhat.com (unknown [10.45.224.33])\n by smtp.corp.redhat.com (Postfix) with ESMTP id 4986D202451F;\n Sat, 30 Mar 2024 17:54:44 +0000 (UTC)"
        ],
        "DKIM-Signature": "v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com;\n s=mimecast20190719; t=1711821289;\n h=from:from:reply-to:subject:subject:date:date:message-id:message-id:\n to:to:cc:cc:mime-version:mime-version:content-type:content-type:\n content-transfer-encoding:content-transfer-encoding;\n bh=P8y169diUrq4AIGlpVXD4tQezCqk+qzyjS60Wb9hkTA=;\n b=WzPHlXETYd9EQbPTB+Ib2EkGhjtLyJTorJjcWciBdP+FyjwivBNC5P68TnS/Nv9gsSItB2\n 4GCr7JicrV/K5SToOcld1E8n7BrRmCiFaBMoNbZYcA0zpV3SnAr43MU+5DMxGQlYiqQijl\n 2Fgr8Xjz/wjxmyQoigU1AcNE6vJ4cZs=",
        "X-MC-Unique": "pkHyIfPfPQid9aOFte1PeA-1",
        "From": "David Marchand <david.marchand@redhat.com>",
        "To": "dev@dpdk.org",
        "Cc": "thomas@monjalon.net, Aaron Conole <aconole@redhat.com>,\n Michael Santana <maicolgabriel@hotmail.com>",
        "Subject": "[PATCH] version: 24.07-rc0",
        "Date": "Sat, 30 Mar 2024 18:54:37 +0100",
        "Message-ID": "<20240330175437.2169948-1-david.marchand@redhat.com>",
        "MIME-Version": "1.0",
        "X-Scanned-By": "MIMEDefang 3.4.1 on 10.11.54.4",
        "X-Mimecast-Spam-Score": "0",
        "X-Mimecast-Originator": "redhat.com",
        "Content-Transfer-Encoding": "8bit",
        "Content-Type": "text/plain; charset=\"US-ASCII\"; x-default=true",
        "X-BeenThere": "dev@dpdk.org",
        "X-Mailman-Version": "2.1.29",
        "Precedence": "list",
        "List-Id": "DPDK patches and discussions <dev.dpdk.org>",
        "List-Unsubscribe": "<https://mails.dpdk.org/options/dev>,\n <mailto:dev-request@dpdk.org?subject=unsubscribe>",
        "List-Archive": "<http://mails.dpdk.org/archives/dev/>",
        "List-Post": "<mailto:dev@dpdk.org>",
        "List-Help": "<mailto:dev-request@dpdk.org?subject=help>",
        "List-Subscribe": "<https://mails.dpdk.org/listinfo/dev>,\n <mailto:dev-request@dpdk.org?subject=subscribe>",
        "Errors-To": "dev-bounces@dpdk.org"
    },
    "content": "Start a new release cycle with empty release notes.\nBump version and ABI minor.\n\nSigned-off-by: David Marchand <david.marchand@redhat.com>\n---\n .github/workflows/build.yml            |   2 +-\n ABI_VERSION                            |   2 +-\n VERSION                                |   2 +-\n doc/guides/rel_notes/index.rst         |   1 +\n doc/guides/rel_notes/release_24_03.rst | 110 --------------------\n doc/guides/rel_notes/release_24_07.rst | 138 +++++++++++++++++++++++++\n 6 files changed, 142 insertions(+), 113 deletions(-)\n create mode 100644 doc/guides/rel_notes/release_24_07.rst",
    "diff": "diff --git a/.github/workflows/build.yml b/.github/workflows/build.yml\nindex 2c308d5e9d..dbf25626d4 100644\n--- a/.github/workflows/build.yml\n+++ b/.github/workflows/build.yml\n@@ -27,7 +27,7 @@ jobs:\n       MINGW: ${{ matrix.config.cross == 'mingw' }}\n       MINI: ${{ matrix.config.mini != '' }}\n       PPC64LE: ${{ matrix.config.cross == 'ppc64le' }}\n-      REF_GIT_TAG: v23.11\n+      REF_GIT_TAG: v24.03\n       RISCV64: ${{ matrix.config.cross == 'riscv64' }}\n       RUN_TESTS: ${{ contains(matrix.config.checks, 'tests') }}\n       STDATOMIC: ${{ contains(matrix.config.checks, 'stdatomic') }}\ndiff --git a/ABI_VERSION b/ABI_VERSION\nindex 0dad123924..9dc0ade502 100644\n--- a/ABI_VERSION\n+++ b/ABI_VERSION\n@@ -1 +1 @@\n-24.1\n+24.2\ndiff --git a/VERSION b/VERSION\nindex 58dfef16ef..2081979127 100644\n--- a/VERSION\n+++ b/VERSION\n@@ -1 +1 @@\n-24.03.0\n+24.07.0-rc0\ndiff --git a/doc/guides/rel_notes/index.rst b/doc/guides/rel_notes/index.rst\nindex 88f2b30b03..77a92b308f 100644\n--- a/doc/guides/rel_notes/index.rst\n+++ b/doc/guides/rel_notes/index.rst\n@@ -8,6 +8,7 @@ Release Notes\n     :maxdepth: 1\n     :numbered:\n \n+    release_24_07\n     release_24_03\n     release_23_11\n     release_23_07\ndiff --git a/doc/guides/rel_notes/release_24_03.rst b/doc/guides/rel_notes/release_24_03.rst\nindex 8e7ad8f99f..013c12f801 100644\n--- a/doc/guides/rel_notes/release_24_03.rst\n+++ b/doc/guides/rel_notes/release_24_03.rst\n@@ -6,55 +6,9 @@\n DPDK Release 24.03\n ==================\n \n-.. **Read this first.**\n-\n-   The text in the sections below explains how to update the release notes.\n-\n-   Use proper spelling, capitalization and punctuation in all sections.\n-\n-   Variable and config names should be quoted as fixed width text:\n-   ``LIKE_THIS``.\n-\n-   Build the docs and view the output file to ensure the changes are correct::\n-\n-      ninja -C build doc\n-      xdg-open build/doc/guides/html/rel_notes/release_24_03.html\n-\n-\n New Features\n ------------\n \n-.. This section should contain new features added in this release.\n-   Sample format:\n-\n-   * **Add a title in the past tense with a full stop.**\n-\n-     Add a short 1-2 sentence description in the past tense.\n-     The description should be enough to allow someone scanning\n-     the release notes to understand the new feature.\n-\n-     If the feature adds a lot of sub-features you can use a bullet list\n-     like this:\n-\n-     * Added feature foo to do something.\n-     * Enhanced feature bar to do something else.\n-\n-     Refer to the previous release notes for examples.\n-\n-     Suggested order in release notes items:\n-     * Core libs (EAL, mempool, ring, mbuf, buses)\n-     * Device abstraction libs and PMDs (ordered alphabetically by vendor name)\n-       - ethdev (lib, PMDs)\n-       - cryptodev (lib, PMDs)\n-       - eventdev (lib, PMDs)\n-       - etc\n-     * Other libs\n-     * Apps, Examples, Tools (if significant)\n-\n-     This section is a comment. Do not overwrite or remove it.\n-     Also, make sure to start the actual text at the margin.\n-     =======================================================\n-\n * **Added HiSilicon UACCE bus support.**\n \n   Added UACCE (Unified/User-space-access-intended Accelerator Framework) bus\n@@ -200,15 +154,6 @@ New Features\n Removed Items\n -------------\n \n-.. This section should contain removed items in this release. Sample format:\n-\n-   * Add a short 1-2 sentence description of the removed item\n-     in the past tense.\n-\n-   This section is a comment. Do not overwrite or remove it.\n-   Also, make sure to start the actual text at the margin.\n-   =======================================================\n-\n * log: Removed the statically defined logtypes that were used internally by DPDK.\n   All code should be using the dynamic logtypes (see ``RTE_LOG_REGISTER()``).\n   The application reserved statically defined logtypes ``RTE_LOGTYPE_USER1..RTE_LOGTYPE_USER8``\n@@ -220,18 +165,6 @@ Removed Items\n API Changes\n -----------\n \n-.. This section should contain API changes. Sample format:\n-\n-   * sample: Add a short 1-2 sentence description of the API change\n-     which was announced in the previous releases and made in this release.\n-     Start with a scope label like \"ethdev:\".\n-     Use fixed width quotes for ``function_names`` or ``struct_names``.\n-     Use the past tense.\n-\n-   This section is a comment. Do not overwrite or remove it.\n-   Also, make sure to start the actual text at the margin.\n-   =======================================================\n-\n * eal: Removed ``typeof(type)`` from the expansion of ``RTE_DEFINE_PER_LCORE``\n   and ``RTE_DECLARE_PER_LCORE`` macros aligning them with their intended design.\n   If use with an expression is desired applications can adapt by supplying\n@@ -249,55 +182,12 @@ API Changes\n ABI Changes\n -----------\n \n-.. This section should contain ABI changes. Sample format:\n-\n-   * sample: Add a short 1-2 sentence description of the ABI change\n-     which was announced in the previous releases and made in this release.\n-     Start with a scope label like \"ethdev:\".\n-     Use fixed width quotes for ``function_names`` or ``struct_names``.\n-     Use the past tense.\n-\n-   This section is a comment. Do not overwrite or remove it.\n-   Also, make sure to start the actual text at the margin.\n-   =======================================================\n-\n * No ABI change that would break compatibility with 23.11.\n \n \n-Known Issues\n-------------\n-\n-.. This section should contain new known issues in this release. Sample format:\n-\n-   * **Add title in present tense with full stop.**\n-\n-     Add a short 1-2 sentence description of the known issue\n-     in the present tense. Add information on any known workarounds.\n-\n-   This section is a comment. Do not overwrite or remove it.\n-   Also, make sure to start the actual text at the margin.\n-   =======================================================\n-\n-\n Tested Platforms\n ----------------\n \n-.. This section should contain a list of platforms that were tested\n-   with this release.\n-\n-   The format is:\n-\n-   * <vendor> platform with <vendor> <type of devices> combinations\n-\n-     * List of CPU\n-     * List of OS\n-     * List of devices\n-     * Other relevant details...\n-\n-   This section is a comment. Do not overwrite or remove it.\n-   Also, make sure to start the actual text at the margin.\n-   =======================================================\n-\n * AMD platforms\n \n   * CPU\ndiff --git a/doc/guides/rel_notes/release_24_07.rst b/doc/guides/rel_notes/release_24_07.rst\nnew file mode 100644\nindex 0000000000..a69f24cf99\n--- /dev/null\n+++ b/doc/guides/rel_notes/release_24_07.rst\n@@ -0,0 +1,138 @@\n+.. SPDX-License-Identifier: BSD-3-Clause\n+   Copyright 2024 The DPDK contributors\n+\n+.. include:: <isonum.txt>\n+\n+DPDK Release 24.07\n+==================\n+\n+.. **Read this first.**\n+\n+   The text in the sections below explains how to update the release notes.\n+\n+   Use proper spelling, capitalization and punctuation in all sections.\n+\n+   Variable and config names should be quoted as fixed width text:\n+   ``LIKE_THIS``.\n+\n+   Build the docs and view the output file to ensure the changes are correct::\n+\n+      ninja -C build doc\n+      xdg-open build/doc/guides/html/rel_notes/release_24_07.html\n+\n+\n+New Features\n+------------\n+\n+.. This section should contain new features added in this release.\n+   Sample format:\n+\n+   * **Add a title in the past tense with a full stop.**\n+\n+     Add a short 1-2 sentence description in the past tense.\n+     The description should be enough to allow someone scanning\n+     the release notes to understand the new feature.\n+\n+     If the feature adds a lot of sub-features you can use a bullet list\n+     like this:\n+\n+     * Added feature foo to do something.\n+     * Enhanced feature bar to do something else.\n+\n+     Refer to the previous release notes for examples.\n+\n+     Suggested order in release notes items:\n+     * Core libs (EAL, mempool, ring, mbuf, buses)\n+     * Device abstraction libs and PMDs (ordered alphabetically by vendor name)\n+       - ethdev (lib, PMDs)\n+       - cryptodev (lib, PMDs)\n+       - eventdev (lib, PMDs)\n+       - etc\n+     * Other libs\n+     * Apps, Examples, Tools (if significant)\n+\n+     This section is a comment. Do not overwrite or remove it.\n+     Also, make sure to start the actual text at the margin.\n+     =======================================================\n+\n+\n+Removed Items\n+-------------\n+\n+.. This section should contain removed items in this release. Sample format:\n+\n+   * Add a short 1-2 sentence description of the removed item\n+     in the past tense.\n+\n+   This section is a comment. Do not overwrite or remove it.\n+   Also, make sure to start the actual text at the margin.\n+   =======================================================\n+\n+\n+API Changes\n+-----------\n+\n+.. This section should contain API changes. Sample format:\n+\n+   * sample: Add a short 1-2 sentence description of the API change\n+     which was announced in the previous releases and made in this release.\n+     Start with a scope label like \"ethdev:\".\n+     Use fixed width quotes for ``function_names`` or ``struct_names``.\n+     Use the past tense.\n+\n+   This section is a comment. Do not overwrite or remove it.\n+   Also, make sure to start the actual text at the margin.\n+   =======================================================\n+\n+\n+ABI Changes\n+-----------\n+\n+.. This section should contain ABI changes. Sample format:\n+\n+   * sample: Add a short 1-2 sentence description of the ABI change\n+     which was announced in the previous releases and made in this release.\n+     Start with a scope label like \"ethdev:\".\n+     Use fixed width quotes for ``function_names`` or ``struct_names``.\n+     Use the past tense.\n+\n+   This section is a comment. Do not overwrite or remove it.\n+   Also, make sure to start the actual text at the margin.\n+   =======================================================\n+\n+* No ABI change that would break compatibility with 23.11.\n+\n+\n+Known Issues\n+------------\n+\n+.. This section should contain new known issues in this release. Sample format:\n+\n+   * **Add title in present tense with full stop.**\n+\n+     Add a short 1-2 sentence description of the known issue\n+     in the present tense. Add information on any known workarounds.\n+\n+   This section is a comment. Do not overwrite or remove it.\n+   Also, make sure to start the actual text at the margin.\n+   =======================================================\n+\n+\n+Tested Platforms\n+----------------\n+\n+.. This section should contain a list of platforms that were tested\n+   with this release.\n+\n+   The format is:\n+\n+   * <vendor> platform with <vendor> <type of devices> combinations\n+\n+     * List of CPU\n+     * List of OS\n+     * List of devices\n+     * Other relevant details...\n+\n+   This section is a comment. Do not overwrite or remove it.\n+   Also, make sure to start the actual text at the margin.\n+   =======================================================\n",
    "prefixes": []
}