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 D31DAA0093 for ; Wed, 9 Mar 2022 08:49:49 +0100 (CET) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id C4ACB40395; Wed, 9 Mar 2022 08:49:49 +0100 (CET) Received: from smtp-relay-internal-1.canonical.com (smtp-relay-internal-1.canonical.com [185.125.188.123]) by mails.dpdk.org (Postfix) with ESMTP id 81BCD40395 for ; Wed, 9 Mar 2022 08:49:48 +0100 (CET) Received: from mail-qk1-f200.google.com (mail-qk1-f200.google.com [209.85.222.200]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by smtp-relay-internal-1.canonical.com (Postfix) with ESMTPS id 058053F222 for ; Wed, 9 Mar 2022 07:49:48 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=canonical.com; s=20210705; t=1646812188; bh=LRh2qGQ2yDxtAWNEKgHX73G+d6Mg8K0dLpPWqTPqN5Q=; h=MIME-Version:References:In-Reply-To:From:Date:Message-ID:Subject: To:Cc:Content-Type; b=enSUSFRAt/YCLGCWqL8hK7Akgza97Dheeq1sflyeGJ8OXNqKRW3tWH3tnHpVdMHwB b6jTZUU4vX/A3uAIIShw4OXeA3p/0a6FdPqpokztjLNq2YHWcctgtEHZ4wzUGVcV8w Bax51X8p7aiNQ8brBrxSQHM+JijgdAjIWhW/UgreCmkona3X2FQcp24GRTwhb3yl/1 y6CpsQs4vub/a1Z87nP+x3WLyWvbEr46pcxxtH8/2jrIsRlxA2Vx3NSwt3zHIuOZoH FKbVdvCvMqzgCOEnkD3WtiINwRN6830HXaHJCyAyhY3QntmMZqsfGlDGJzZ8rEa6/0 Hprd7QhjUSG5A== Received: by mail-qk1-f200.google.com with SMTP id s12-20020a05620a030c00b0064971887744so1027958qkm.8 for ; Tue, 08 Mar 2022 23:49:47 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=LRh2qGQ2yDxtAWNEKgHX73G+d6Mg8K0dLpPWqTPqN5Q=; b=vlVERMwd9VpT0nEu6ymwRNPLt/T3J1r7PmXVnIKaif0JxiLC5SH572+nuMnI5q1iKg DyZ4qKzTWjjLFS4GRHl8p9V1rey3nmAjhXikiiStueHryDn4b1dzQVClhWCIvE8eeFy0 V/U5mNxg25WsqpJ0Mv6AOVI03RdZWLMXrKvhKc1JX8m7ZgdxpiEKSZQ8Q4FzfsTEH0S5 K6vAzY2xhMS37EVOtNsXHUc6RvXpuEr9hj5qsCknQKFBgrX21DQSqdTAKaBcjSroN1PY DTA3FfPeYWGR3XIPtE8csKY8FdqMVL19d4iJg/At4lMBY+7p9+wy1nNQhXwziqrakgaZ rOdQ== X-Gm-Message-State: AOAM5339CSc5tsIKdfj+5Qjcz9WB5EHifbkaDSZZ7oU6wYyKxYSpgUsN ibBapaRRmiyclRrK8KR46vNo0XIOMpWxR/IERRebnBlqpSx5zvMVhITtduN1HSE4sRuTvkeSCTO kRQSQ2/zOqq8rjOPbAMLh1WYeDuZXYfQVBIrYj1TK X-Received: by 2002:ac8:5c45:0:b0:2e1:9144:2849 with SMTP id j5-20020ac85c45000000b002e191442849mr2676094qtj.510.1646812186292; Tue, 08 Mar 2022 23:49:46 -0800 (PST) X-Google-Smtp-Source: ABdhPJwNIs4nIkjwR1oxTlHz3dcUO+4bDSgCY2hOaTQrytSBfhNpD3t50EBA3A3pDn5ci2LR8q6K243KI4ZXO4jdHYc= X-Received: by 2002:ac8:5c45:0:b0:2e1:9144:2849 with SMTP id j5-20020ac85c45000000b002e191442849mr2676088qtj.510.1646812186106; Tue, 08 Mar 2022 23:49:46 -0800 (PST) MIME-Version: 1.0 References: <20220225171532.3498996-1-christian.ehrhardt@canonical.com> In-Reply-To: From: Christian Ehrhardt Date: Wed, 9 Mar 2022 08:49:20 +0100 Message-ID: Subject: Re: please help backporting some patches to stable release 19.11.12 - part II To: Josh Soref Cc: dpdk stable Content-Type: text/plain; charset="UTF-8" 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: , Errors-To: stable-bounces@dpdk.org On Fri, Feb 25, 2022 at 6:54 PM Josh Soref wrote: > > Christian Ehrhardt wrote: > > 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 19.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 19.11 branch, or > - Indicate that the patch should not be backported > > > My spelling work can be safely skipped. Thank you for the FYI Maybe to everyone let me explain the reason why we even try :-) In general those kinds of fixes are not "too important" but if they can be applied it keeps the amount of extra churn lower later on. Imagine you touch every string with a commit, afterwards nothing will apply automatically anymore. So sometimes backporting those changes even if they feel "not important" can help. >> Please do either of the above by 03/11/22. -- Christian Ehrhardt Staff Engineer, Ubuntu Server Canonical Ltd