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 EFAC94624E for ; Mon, 17 Feb 2025 18:13:30 +0100 (CET) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id E4847402D5; Mon, 17 Feb 2025 18:13:30 +0100 (CET) Received: from mail-wr1-f49.google.com (mail-wr1-f49.google.com [209.85.221.49]) by mails.dpdk.org (Postfix) with ESMTP id 5FAB5402D5 for ; Mon, 17 Feb 2025 18:13:29 +0100 (CET) Received: by mail-wr1-f49.google.com with SMTP id ffacd0b85a97d-38f31f7732dso1671681f8f.1 for ; Mon, 17 Feb 2025 09:13:29 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1739812409; x=1740417209; darn=dpdk.org; h=content-transfer-encoding:reply-to:mime-version:message-id:date :subject:cc:to:from:from:to:cc:subject:date:message-id:reply-to; bh=500eXC7PxrJdCwxwH8ArRy88O5eUGRoPXFDjq5qLRPE=; b=OeLahaH6GrOrlcBPF0YU1bEJRMKk8HxZ9cEZYN9HEVTkc4B4Ohf1jdD5Nbs4ntLIsF mFNLshxN1vSJ6wpDFyspWYXOxYNYX+bkDUrhhIGyRH53seOZBmjegn6oyP9uDy31vnS3 O3FxC/PHNdTRe06AN8irxW2TaGG4swpLzjNVu8i5alxcjvN5GHtSQUMAjBQPJHeRMKZY YHBQ9Xz6EYszdKlEHTH86VI9X8aUsvWM1uSVIxX6DUxCNbedZPlby4szXVlx0c32nmFj HrInQ87xfsFzbgM56tO6U7hq/03+3AuWCaeL98HM8OJk+nRdcLniBapi7/O1VHvkqTYi lAXg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1739812409; x=1740417209; h=content-transfer-encoding:reply-to:mime-version:message-id:date :subject:cc:to:from:x-gm-message-state:from:to:cc:subject:date :message-id:reply-to; bh=500eXC7PxrJdCwxwH8ArRy88O5eUGRoPXFDjq5qLRPE=; b=SfbOsM8u4BPbkUQFmOUbM22c0wNX6bXvEVy2lTk4Ac7Wo/b2Yll34JfvIZkXN+Nqk8 BAS85V/arPpZojGxLSuaZXV5aYHBDrHL30zbleVPUj/NDWqOd3VFrO4K9+B3POXwTTp0 EqEfyXKtpb3i1TIUlJKZZcOqq+4E9jTFCRESc4tI1dnjgF3qDe2tPDwSbXCM7EjMayIe 8FvjpabEFBNTNYZPgJyln0BnT5xC4HfqJhogXKQSY3EaEKaPKwNS6ueUumFKKWjRjvAY tmBuroGI02iSz10HPB7aih/A/BHREL/jT9Gn+H+i3E0Cw9SSFOwKN1jyAMC5RaIdaoBL JUGA== X-Gm-Message-State: AOJu0YyVeiXpnabUuWC7LVEOY5AwXHGHmJh1FD82gM04buZYWTMufoeC HG698xB6NrpXEpUi6rvBra1aCpNLdIGI7+8WawV7BBBiP7Ev+wqrUIG7CE65Ye1g7A== X-Gm-Gg: ASbGncs54RvKTcSDsmaTEHEaEupks/MROXiwmMjj4RsaSqcV5dYfwN9SUgJBFLK6Km3 uXjH5ZgF9215HHa2JTeYoKA3A/6JigG1NRDDDHMubECyJGkiOVs4Ill0yV3LN1LlSoYpQcPZvLr akhrAT9i1qrIlgI4imCFJQ/JCTDKDwLcyIVTgbTOWhPnQ2uGxhvlBNsn6qQNpMGelTLt3wCKrei AVZXdDNcMcp9qLLxKINYlDJvC52hlOj5VDfQXgLKMfT0polFp+pnF26AOSX+Gn0YpPJOG7qMgtV g6TphUCeYsPTKw2HXWm3lA== X-Google-Smtp-Source: AGHT+IFOT5n0+cyxQ84fqyp8E8OPk/lF10MLW1uOeRvc5C3fgKC3vXttCv8OKNCFgsB2aM3XqgSkbA== X-Received: by 2002:a5d:6f19:0:b0:38d:e420:3942 with SMTP id ffacd0b85a97d-38f24ce772emr19360331f8f.3.1739812408697; Mon, 17 Feb 2025 09:13:28 -0800 (PST) Received: from localhost ([2a01:4b00:d036:ae00:f83c:95e7:29fd:a997]) by smtp.gmail.com with UTF8SMTPSA id ffacd0b85a97d-38f259f8730sm13085709f8f.93.2025.02.17.09.13.28 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Mon, 17 Feb 2025 09:13:28 -0800 (PST) From: luca.boccassi@gmail.com To: dpdk stable Cc: Bruce Richardson , Chas Williams , Chenbo Xia , Chengwen Feng , David Marchand , Huisong Li , Joshua Washington , Junfeng Guo , Lingli Chen , Maxime Coquelin , Maxime Gouin , "Min Hu (Connor)" , Olivier Matz , Praveen Kaligineedi , Raslan Darawsheh , Stephen Hemminger , Xiaoyun Li Subject: please help backporting some patches to stable release 22.11.8 Date: Mon, 17 Feb 2025 17:13:24 +0000 Message-ID: <20250217171326.1069702-1-luca.boccassi@gmail.com> X-Mailer: git-send-email 2.47.2 MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-BeenThere: stable@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: patches for DPDK stable branches List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Reply-To: dpdk stable Errors-To: stable-bounces@dpdk.org Hi commit authors (and maintainers), Despite being selected by the DPDK maintenance tool ./devtools/git-log-fixes.sh I didn't apply following commits from DPDK main to 22.11 stable branch, as conflicts or build errors occur. Can authors check your patches in the following list and either: - Backport your patches to the 22.11 branch, or - Indicate that the patch should not be backported Please do either of the above by 2025/02/24. You can find the a temporary work-in-progress branch of the coming 22.11.8 release at: https://github.com/bluca/dpdk-stable It is recommended to backport on top of that to minimize further conflicts or misunderstandings. Some notes on stable backports: A backport should contain a reference to the DPDK main branch commit in it's commit message in the following fashion: [ upstream commit ] For example: https://git.dpdk.org/dpdk-stable/commit/?h=18.11&id=d90e6ae6f936ecdc2fd3811ff9f26aec7f3c06eb When sending the backported patch, please indicate the target branch in the subject line, as we have multiple branches, for example: [PATCH 22.11] foo/bar: fix baz With git format-patch, this can be achieved by appending the parameter: --subject-prefix='PATCH 22.11' Send the backported patch to "stable@dpdk.org" but not "dev@dpdk.org". FYI, branch 22.11 is located at tree: https://git.dpdk.org/dpdk-stable Thanks. Luca Boccassi --- 4dc4e33ffa Olivier Matz net/virtio: fix Rx checksum calculation a71168a775 Praveen Kaligineedi net/gve: allocate Rx QPL pages using malloc eb29e625ce Stephen Hemminger test/bonding: fix active backup receive test