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 3346DA04DD for ; Wed, 28 Oct 2020 12:20:28 +0100 (CET) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id 1B912CB4A; Wed, 28 Oct 2020 12:20:27 +0100 (CET) Received: from mail-wr1-f65.google.com (mail-wr1-f65.google.com [209.85.221.65]) by dpdk.org (Postfix) with ESMTP id 90699CB4A for ; Wed, 28 Oct 2020 12:20:24 +0100 (CET) Received: by mail-wr1-f65.google.com with SMTP id m13so977660wrj.7 for ; Wed, 28 Oct 2020 04:20:24 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:message-id:subject:from:to:cc:date:in-reply-to :references:content-transfer-encoding:user-agent:mime-version; bh=kF5Xu3GeBqtgBS75qRh5wLqp5llHNpKNyCGZnEwz73U=; b=nP1viHJ8L6B3ZVPhWqouXQ6TpGie7vWUYf/upWoIsvv7U/xONEqdSZ9G4bzFhkze/X CizWzDjpoZyR9hFEspxKHFkOYcJHh063LDB8yzcTvdtM6TTA4Cwldl5L/kp2clAc0P9R u4l4k/3Mqozu5aohhNZtoydxOC8m0LPBT6GUQDtFkHWAZJFoPhACak8kQm6k+ODOOO4R GhJTR+hll6peyGjfU7FKNzEYPYkI004mKtImlfvBz2bbH2GZhtBF4Jp5sYodQ4ZhidB3 AJjvhXX+ohOt6qx79J9x5lpBXvkOsJXKpizndufwL9VwSR/hIFPZjGEwUPz7DKjs8jOZ 3Ckw== X-Gm-Message-State: AOAM532GeYyWUkaqtFivdasNxsxyAsGZ12WD0iDBWVIWf/PKwDQmiI8o 3OS22tXS6aoQ8bGbE0oN4iY= X-Google-Smtp-Source: ABdhPJwWqyRTW6JasaVlee+DiBbqQk35N2xW9nOaJpdHw1UK+T4qpLnFSscK/DqaqAoK8SvAjcAIGg== X-Received: by 2002:adf:fe8b:: with SMTP id l11mr8644115wrr.9.1603884024271; Wed, 28 Oct 2020 04:20:24 -0700 (PDT) Received: from localhost ([88.98.246.218]) by smtp.gmail.com with ESMTPSA id b5sm6370335wrs.97.2020.10.28.04.20.23 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Wed, 28 Oct 2020 04:20:23 -0700 (PDT) Message-ID: From: Luca Boccassi To: Qi Zhang Cc: stable@dpdk.org, ferruh.yigit@intel.com, Wei Zhao Date: Wed, 28 Oct 2020 11:20:23 +0000 In-Reply-To: <20201010025315.728589-1-qi.z.zhang@intel.com> References: <20201010025315.728589-1-qi.z.zhang@intel.com> Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable User-Agent: Evolution 3.30.5-1.1 MIME-Version: 1.0 Subject: Re: [dpdk-stable] [PATCH v2] net/iavf: support multicast configuration 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" On Sat, 2020-10-10 at 10:53 +0800, Qi Zhang wrote: > [ upstream commit 05e4c3aff35f41d527acfab86df55477fd8dcff2 ] >=20 > This patch enable add multicast address for iavf. >=20 > Signed-off-by: Wei Zhao > Acked-by: Qi Zhang > --- >=20 > To maintainer: >=20 > I know this is not a fix, but this is requested by an important > customer that will use DPDK 19.11 LTS, meanwhile this patch just add a mi= ssing > eth_dev op in AVF, it has low risk to bring any side effect. >=20 > doc/guides/nics/features/iavf.ini | 1 + > drivers/net/iavf/iavf.h | 7 ++++ > drivers/net/iavf/iavf_ethdev.c | 43 ++++++++++++++++++++++++ > drivers/net/iavf/iavf_vchnl.c | 56 +++++++++++++++++++++++++++++++ > 4 files changed, 107 insertions(+) Next time please follow the guidelines and use --subject-prefix=3D'PATCH 19.11' when sending, otherwise the mail gets filtered out. What happens if someone upgrades from 19.11.6 with this patch, to say 20.08 which doesn't have it? Are there hard errors, or will the feature simply be ignored? --=20 Kind regards, Luca Boccassi