Received: by 2002:a05:7412:d024:b0:f9:90c9:de9f with SMTP id bd36csp164123rdb; Wed, 20 Dec 2023 08:54:49 -0800 (PST) X-Google-Smtp-Source: AGHT+IGdcVALSnEqDD5bAhD0orLkLScd6NQdCmFfSYWDzT7xNhygG8oBhFvOGhYQ9Sxw6fbtcnIQ X-Received: by 2002:a05:6870:d623:b0:1fb:5e84:c669 with SMTP id a35-20020a056870d62300b001fb5e84c669mr4644oaq.25.1703091289123; Wed, 20 Dec 2023 08:54:49 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1703091289; cv=none; d=google.com; s=arc-20160816; b=RaNuQBqnGJvbzmh6ILWcmWQjhe50WrVowAjso1llF6siz4FUQzEiNkVm+1My5xYFEv VFsbdPDllCoH57J5efaQ4FkaflYnXAPwRKE9+ToapqBmRpjMdwN5bODx5U6zSvZEDFxE HCQrL703QxFzk4assZ7kCDAe2yAytVH9fupVzgK1gnHkR3SIlb6lTJNLs1fWC5ZwGj/H WtoiXgnIvNAJwUVt8DVrqmU7n+OXQ4i41R7pF0DzFK2Mv2JaKHfF+eUwg1hMyTQiCMwY Xa1zIXitsohxAsJXsz4O+oTgwe37Ux5bZeAqvaVpjebtV1Ts6x3qFKxE1wu2RVoxqRSm FJlg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=in-reply-to:content-disposition:mime-version:list-unsubscribe :list-subscribe:list-id:precedence:references:message-id:subject:cc :to:from:date:dkim-signature; bh=VP7AW7HYQ8HFKL4JUw0s/3irljCG9KXmFoTdTfrvcJA=; fh=5e3xSpjQjSz2zDgMMYlfgrv7RCxdYPwXGYn10/lDRSI=; b=i+1W1OJo5oalXDNvZL7i0qxO0B9Xz6FpuN52IX4hyvoYgRK9Uzh8+JCc3UJRzy0x8X SarLV573rC2o3fLMrTKaRGJELOV+L+ruNmlhg2zb3bu5Q3mJ7NhPNfS7FBvmocnDifNj WrQR1GCAxAXK1GGbqW0VYrxyO6TYzB5/E7ruByvVcrh5kXhS/uO9KODkyfZEMB6dTrRu b3VwJf1CUC39FF2Rv0jN/s+u9gr1KjWFJHwKnVHarb6OM0qCCdXuofNZBfE05GYF7UTt tRScLkVq5wkvmNdUe/58KVE7whh1j+6ipPNFaVitpd8EnMxW+RkrpcQCFs1zvloQ0R8k NQwQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=k20201202 header.b=h7KVYkhe; spf=pass (google.com: domain of linux-kernel+bounces-7324-linux.lists.archive=gmail.com@vger.kernel.org designates 2604:1380:45d1:ec00::1 as permitted sender) smtp.mailfrom="linux-kernel+bounces-7324-linux.lists.archive=gmail.com@vger.kernel.org"; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Return-Path: Received: from ny.mirrors.kernel.org (ny.mirrors.kernel.org. [2604:1380:45d1:ec00::1]) by mx.google.com with ESMTPS id b13-20020a0cc98d000000b0067f2120275dsi67788qvk.542.2023.12.20.08.54.48 for (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Wed, 20 Dec 2023 08:54:49 -0800 (PST) Received-SPF: pass (google.com: domain of linux-kernel+bounces-7324-linux.lists.archive=gmail.com@vger.kernel.org designates 2604:1380:45d1:ec00::1 as permitted sender) client-ip=2604:1380:45d1:ec00::1; Authentication-Results: mx.google.com; dkim=pass header.i=@kernel.org header.s=k20201202 header.b=h7KVYkhe; spf=pass (google.com: domain of linux-kernel+bounces-7324-linux.lists.archive=gmail.com@vger.kernel.org designates 2604:1380:45d1:ec00::1 as permitted sender) smtp.mailfrom="linux-kernel+bounces-7324-linux.lists.archive=gmail.com@vger.kernel.org"; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Received: from smtp.subspace.kernel.org (wormhole.subspace.kernel.org [52.25.139.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ny.mirrors.kernel.org (Postfix) with ESMTPS id 21A811C208DD for ; Wed, 20 Dec 2023 16:54:47 +0000 (UTC) Received: from localhost.localdomain (localhost.localdomain [127.0.0.1]) by smtp.subspace.kernel.org (Postfix) with ESMTP id CC8B44777A; Wed, 20 Dec 2023 16:54:01 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b="h7KVYkhe" X-Original-To: linux-kernel@vger.kernel.org Received: from smtp.kernel.org (aws-us-west-2-korg-mail-1.web.codeaurora.org [10.30.226.201]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 0194D46544; Wed, 20 Dec 2023 16:54:00 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id 60CE5C433C7; Wed, 20 Dec 2023 16:53:56 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1703091240; bh=O34EsK513kFHp7fAXRySvU2fS0ZbVOxsvU6nxPXlp9Y=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=h7KVYkheDrV2GSmecwZmWYAqc5lBZ66M2CJLxIwyvK0yNk/ewCmbsFAvcxsuhdTHJ s2CJsxwkFljgzBD91jpBlUAmbQgMmWjpCO5fvz0cEv3SAfdM4bCOZp5dfFQqy91f0g nycICGdJZ3zyPkroCKIfudXfnOM8Aktd7QECdbfmcDkERiZ0bBIvr7ftJdgV27ZH1D mcLMiSvloX9NDzkO8f/SbNHuVssWQgmQf3ZFUlzoLgieu9wUSRI+ND8Iph9qVzcHKB AKq+upneolXlCOGj/bQBzugj1CUPSARyN4JDmxIruNpHgNdhKwAJWN9ufnA7QA8nGc d52UJaY2+ogNA== Date: Wed, 20 Dec 2023 17:53:52 +0100 From: Simon Horman To: Lin Ma Cc: roopa@nvidia.com, razor@blackwall.org, davem@davemloft.net, edumazet@google.com, kuba@kernel.org, pabeni@redhat.com, horatiu.vultur@microchip.com, henrik.bjoernlund@microchip.com, bridge@lists.linux.dev, netdev@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH v1] bridge: cfm: fix enum typo in br_cc_ccm_tx_parse Message-ID: <20231220165352.GO882741@kernel.org> References: <20231220075914.2426376-1-linma@zju.edu.cn> <20231220161742.GM882741@kernel.org> <55cdc6e4.49734.18c880f5a2f.Coremail.linma@zju.edu.cn> Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <55cdc6e4.49734.18c880f5a2f.Coremail.linma@zju.edu.cn> On Thu, Dec 21, 2023 at 12:29:16AM +0800, Lin Ma wrote: > Hello Simon, > > > > > Thanks Lin Ma, > > > > I agree with your analysis, that the problem was introduced in the > > cited commit, and that it is resolved by your patch. > > > > Thanks for the encouragement. > > > However, as there is no user-visible bug I don't believe this reaches > > the bar for a 'fix' for Networking code. Accordingly, I think that > > the Fixes tag should be dropped. And, instead cited commit can be mentioned > > using something like "This problem was introduced by commit ...". > > > > Also, as I don't think it is a fix I think it should be targeted at the > > net-next tree: > > > > Subject: [PATCH net-next vX] ... > > > > Copy that. Yeah, once the enum IFLA_BRIDGE_CFM_CC_RDI_INSTANCE and the > IFLA_BRIDGE_CFM_CC_CCM_TX_INSTANCE keeps the value 1, everything should work > as usual. I will resend the patch as told. Thanks, much appreciated. v2 looks good to me. > > > The above nits notwithstanding, > > > > Reviewed-by: Simon Horman > > > > Regards > Lin