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 30DDCA0093 for ; Thu, 28 May 2020 18:24:45 +0200 (CEST) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id 2778F1DC10; Thu, 28 May 2020 18:24:45 +0200 (CEST) Received: from us-smtp-1.mimecast.com (us-smtp-delivery-1.mimecast.com [205.139.110.120]) by dpdk.org (Postfix) with ESMTP id D62561DC18 for ; Thu, 28 May 2020 18:24:41 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1590683081; 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=MyrwEE3kwVz0sjq9Kr6R+HhsqrZth7uzN/sJxWaroXo=; b=QsQKcLqMtggFP05EjQmowZguac8GHNtGtQRi18fPfzLmMUHBK193pjKcJa1XMhOQQDTIcG OTbJJ6pplGImQUkPvZWMvthgh40/GLeiCFbrYzGRtSl5VrZuRwSJqJiu/FWCOCXSRGycHq +glXPkurtEnzxClyb3YC1cfE5QvkEwU= Received: from mimecast-mx01.redhat.com (mimecast-mx01.redhat.com [209.132.183.4]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-266-kDqv0FeoMWu1hYnf0XV1mg-1; Thu, 28 May 2020 12:24:29 -0400 X-MC-Unique: kDqv0FeoMWu1hYnf0XV1mg-1 Received: from smtp.corp.redhat.com (int-mx02.intmail.prod.int.phx2.redhat.com [10.5.11.12]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx01.redhat.com (Postfix) with ESMTPS id 0A0398018A7; Thu, 28 May 2020 16:24:28 +0000 (UTC) Received: from rh.redhat.com (unknown [10.33.36.235]) by smtp.corp.redhat.com (Postfix) with ESMTP id 50D3B60C87; Thu, 28 May 2020 16:24:26 +0000 (UTC) From: Kevin Traynor To: Gaetan Rivet Cc: dpdk stable Date: Thu, 28 May 2020 17:21:57 +0100 Message-Id: <20200528162322.7863-10-ktraynor@redhat.com> In-Reply-To: <20200528162322.7863-1-ktraynor@redhat.com> References: <20200528162322.7863-1-ktraynor@redhat.com> MIME-Version: 1.0 X-Scanned-By: MIMEDefang 2.79 on 10.5.11.12 X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 8bit Subject: [dpdk-stable] patch 'doc: fix number of failsafe sub-devices' has been queued to LTS release 18.11.9 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 LTS release 18.11.9 Note it hasn't been pushed to http://dpdk.org/browse/dpdk-stable yet. It will be pushed if I get no objections before 06/03/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. Queued patches are on a temporary branch at: https://github.com/kevintraynor/dpdk-stable-queue This queued commit can be viewed at: https://github.com/kevintraynor/dpdk-stable-queue/commit/8d329ee587cb2820d75de20babc039fa94e02729 Thanks. Kevin. --- >From 8d329ee587cb2820d75de20babc039fa94e02729 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 @@ -50,5 +50,5 @@ The Fail-safe PMD can be used like most other DPDK virtual devices, by passing a 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 -- 2.21.3 --- Diff of the applied patch vs upstream commit (please double-check if non-empty: --- --- - 2020-05-28 17:12:59.703710665 +0100 +++ 0010-doc-fix-number-of-failsafe-sub-devices.patch 2020-05-28 17:12:59.047557622 +0100 @@ -1 +1 @@ -From c4169faf9dab18d164557e2b52f7ba1e9d6b768f Mon Sep 17 00:00:00 2001 +From 8d329ee587cb2820d75de20babc039fa94e02729 Mon Sep 17 00:00:00 2001 @@ -5,0 +6,2 @@ +[ upstream commit c4169faf9dab18d164557e2b52f7ba1e9d6b768f ] + @@ -10 +11,0 @@ -Cc: stable@dpdk.org @@ -18 +19 @@ -index 3ce2f8bee3..b4a92f663b 100644 +index 6c02d7ef6d..60bbf40f7f 100644 @@ -27 +28 @@ - 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