From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from dpdk.org (dpdk.org [92.243.14.124]) by inbox.dpdk.org (Postfix) with ESMTP id 5EAA7A0093 for ; Tue, 19 May 2020 14:59:12 +0200 (CEST) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id 56B881C1E4; Tue, 19 May 2020 14:59:12 +0200 (CEST) Received: from mail-wm1-f67.google.com (mail-wm1-f67.google.com [209.85.128.67]) by dpdk.org (Postfix) with ESMTP id 5E4521D621 for ; Tue, 19 May 2020 14:59:11 +0200 (CEST) Received: by mail-wm1-f67.google.com with SMTP id n18so3435461wmj.5 for ; Tue, 19 May 2020 05:59:11 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:to:cc:subject:date:message-id:in-reply-to:references :mime-version:content-transfer-encoding; bh=0+ONGjlosSDRFoIGHQyapv0mhJDe7UzEDWQGoTSTI88=; b=tlcmtJ1b4IuJMGYERW7bdniQ3fxZ+nOtsuLiAEBQgw74I7bP9f4sL/KtjDtyMOmoBc XCeMbva83ADLX/Viz1N7tar0JfzQrkeS989uFi+q8ne6XGJQWsIoxZbDTotwzp9q1loT WHXyMWIRWpdPnjGJUgAa1VGM6Ax8HeInGVxzlKF+V4iGCYAr9YbL/fyiUlLCBHT6AjCc XViJeLC5ELdNAHLESlo2dh7uSYbOsRj0KBvk7mA/1LHIde6F7r6Z0Z13sU944tynF1wk WGycPj2gF85RO7EkiRUMgPXD3dN8x5NQN4JN3z6H012P9jJpCEkl3MXH5RyUcthF4+vQ veHQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:cc:subject:date:message-id:in-reply-to :references:mime-version:content-transfer-encoding; bh=0+ONGjlosSDRFoIGHQyapv0mhJDe7UzEDWQGoTSTI88=; b=ffclgx4KOuDqF+S2axAofMVHs83013TNHa7oOaVoi6NjDBuog341pxGRj/Z1Sb22Av hPu+KwmfjWwTbIp3KxIeahJqsyi/tCvf/Z7czjwTgbQPDR3qyByq8kp9reQ/6wLiykK9 H+wmJkDgsqXuBRm3/gARt2Hxs0vqOtXeGd10FfDuIQ43+N/WWwaoW3czphfMArrqkjk1 sAA6y4yurN8aKP/HY7XgmM78DU0fFmPNDai1Gcwsdb2bi1WwFUWZJw764xC1sIblxzou muwyhqSKQqaXhMAFioquXHsAIrVNvZEaLr5sKHBUjQ2+4dZ6O0+Koi8Km/KLPWj3fyqY U1uw== X-Gm-Message-State: AOAM531WllKscoePodneonZ+IgSrSEeqFdgntpeYUCFH2YEeP2ZIz66+ Mi+t8EZfTnEQqNr1LZR3nTJvNm+X7S0M1W+2 X-Google-Smtp-Source: ABdhPJyIVBhcevVtSgPFn+2jWu6W6eF6GWa4dTK3oYYTgXe55xZD10YZLVgoTPPjzqF2buQ/B7EfIQ== X-Received: by 2002:a7b:c24b:: with SMTP id b11mr5309964wmj.101.1589893151131; Tue, 19 May 2020 05:59:11 -0700 (PDT) Received: from localhost ([88.98.246.218]) by smtp.gmail.com with ESMTPSA id n17sm20497019wrr.42.2020.05.19.05.59.10 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Tue, 19 May 2020 05:59:10 -0700 (PDT) From: luca.boccassi@gmail.com To: Gaetan Rivet Cc: dpdk stable Date: Tue, 19 May 2020 13:53:35 +0100 Message-Id: <20200519125804.104349-25-luca.boccassi@gmail.com> X-Mailer: git-send-email 2.20.1 In-Reply-To: <20200519125804.104349-1-luca.boccassi@gmail.com> References: <20200519125804.104349-1-luca.boccassi@gmail.com> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Subject: [dpdk-stable] patch 'doc: fix number of failsafe sub-devices' has been queued to stable release 19.11.3 X-BeenThere: stable@dpdk.org X-Mailman-Version: 2.1.15 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 Sender: "stable" Hi, FYI, your patch has been queued to stable release 19.11.3 Note it hasn't been pushed to http://dpdk.org/browse/dpdk-stable yet. It will be pushed if I get no objections before 05/21/20. So please shout if anyone has objections. Also note that after the patch there's a diff of the upstream commit vs the patch applied to the branch. This will indicate if there was any rebasing needed to apply to the stable branch. If there were code changes for rebasing (ie: not only metadata diffs), please double check that the rebase was correctly done. Thanks. Luca Boccassi --- >From 194ca60cde179bae1f88b4eb87fddac20c60cfae Mon Sep 17 00:00:00 2001 From: Gaetan Rivet Date: Sat, 22 Feb 2020 01:14:40 +0100 Subject: [PATCH] doc: fix number of failsafe sub-devices [ upstream commit c4169faf9dab18d164557e2b52f7ba1e9d6b768f ] Supporting more than 2 sub-device is a remnant from earlier fail-safe design, that was never actually published. Fixes: a46f8d584eb8 ("net/failsafe: add fail-safe PMD") Signed-off-by: Gaetan Rivet --- doc/guides/nics/fail_safe.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/guides/nics/fail_safe.rst b/doc/guides/nics/fail_safe.rst index 6c02d7ef6d..60bbf40f7f 100644 --- a/doc/guides/nics/fail_safe.rst +++ b/doc/guides/nics/fail_safe.rst @@ -49,7 +49,7 @@ The Fail-safe PMD can be used like most other DPDK virtual devices, by passing a ``--vdev`` parameter to the EAL when starting the application. The device name must start with the *net_failsafe* prefix, followed by numbers or letters. This name must be unique for each device. Each fail-safe instance must have at least one -sub-device, up to ``RTE_MAX_ETHPORTS-1``. +sub-device, and at most two. A sub-device can be any legal DPDK device, including possibly another fail-safe instance. -- 2.20.1 --- Diff of the applied patch vs upstream commit (please double-check if non-empty: --- --- - 2020-05-19 13:56:19.838172744 +0100 +++ 0025-doc-fix-number-of-failsafe-sub-devices.patch 2020-05-19 13:56:18.207501603 +0100 @@ -1,13 +1,14 @@ -From c4169faf9dab18d164557e2b52f7ba1e9d6b768f Mon Sep 17 00:00:00 2001 +From 194ca60cde179bae1f88b4eb87fddac20c60cfae Mon Sep 17 00:00:00 2001 From: Gaetan Rivet Date: Sat, 22 Feb 2020 01:14:40 +0100 Subject: [PATCH] doc: fix number of failsafe sub-devices +[ upstream commit c4169faf9dab18d164557e2b52f7ba1e9d6b768f ] + Supporting more than 2 sub-device is a remnant from earlier fail-safe design, that was never actually published. Fixes: a46f8d584eb8 ("net/failsafe: add fail-safe PMD") -Cc: stable@dpdk.org Signed-off-by: Gaetan Rivet --- @@ -15,7 +16,7 @@ 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/guides/nics/fail_safe.rst b/doc/guides/nics/fail_safe.rst -index 3ce2f8bee3..b4a92f663b 100644 +index 6c02d7ef6d..60bbf40f7f 100644 --- a/doc/guides/nics/fail_safe.rst +++ b/doc/guides/nics/fail_safe.rst @@ -49,7 +49,7 @@ The Fail-safe PMD can be used like most other DPDK virtual devices, by passing a @@ -25,8 +26,8 @@ -sub-device, up to ``RTE_MAX_ETHPORTS-1``. +sub-device, and at most two. - A sub-device can be any DPDK device, including possibly another fail-safe device. - + A sub-device can be any legal DPDK device, including possibly another fail-safe + instance. -- 2.20.1