[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20231220165352.GO882741@kernel.org>
Date: Wed, 20 Dec 2023 17:53:52 +0100
From: Simon Horman <horms@...nel.org>
To: Lin Ma <linma@....edu.cn>
Cc: roopa@...dia.com, razor@...ckwall.org, davem@...emloft.net,
edumazet@...gle.com, kuba@...nel.org, pabeni@...hat.com,
horatiu.vultur@...rochip.com, henrik.bjoernlund@...rochip.com,
bridge@...ts.linux.dev, netdev@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH v1] bridge: cfm: fix enum typo in br_cc_ccm_tx_parse
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 <horms@...nel.org>
> >
>
> Regards
> Lin
Powered by blists - more mailing lists