From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: DKIM-Filter: OpenDKIM Filter v2.11.0 smtp2.osuosl.org E42A0405DB DKIM-Filter: OpenDKIM Filter v2.11.0 smtp2.osuosl.org CDB31405BC DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1666631284; bh=qWgfUtE4UN4/iCrWAyctAyzwt74lHMnUej7miAfWozs=; h=Date:From:To:Cc:Subject:In-Reply-To:References:From; b=Zu+kqShRcjC8nRPj+ZPavRcjYG48rUxYr/xtUKVxq/tVD3qP4BQ8938gc4JRHh+sQ wUEoCQstYbywkycJbXo1Gx9NudXpA31ePGv1ymKF7AziAkUafYLdFNwgeHV1QImOEK JFwJgG3tBQ+MqnkxeUpIBTBFzGPMlWiBuQYZJPplfyUZSfiekZhXplF9BCf4TEz5cR BoSuO18xOEhTlK5W4tnJUnjIc+5268Ad/+OGpyLVWX/qO+ewTt1u6BRu/hvzFkn3Kl CbW0He1dZ/toR97u7dANoXILUr18MDMSTzT2iOWvvh3xihpjn8Gr15icEr7MzFt17l NwXsJuVW8BO6Q== Date: Mon, 24 Oct 2022 10:08:01 -0700 From: Jakub Kicinski Message-ID: <20221024100801.6c391ff9@kernel.org> In-Reply-To: <7690b7f836b144b60f60b3b68d3bf784@kapio-technology.com> References: <20221018165619.134535-1-netdev@kapio-technology.com> <20221018165619.134535-3-netdev@kapio-technology.com> <7690b7f836b144b60f60b3b68d3bf784@kapio-technology.com> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Subject: Re: [Bridge] [PATCH v8 net-next 02/12] net: bridge: add blackhole fdb entry flag List-Id: Linux Ethernet Bridging List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: netdev@kapio-technology.com Cc: Andrew Lunn , Alexandre Belloni , Nikolay Aleksandrov , Kurt Kanzenbach , Eric Dumazet , linux-kselftest@vger.kernel.org, Joachim Wiberg , Shuah Khan , Ivan Vecera , Florian Fainelli , Daniel Borkmann , Florent Fourcot , bridge@lists.linux-foundation.org, Russell King , linux-arm-kernel@lists.infradead.org, Ido Schimmel , Paolo Abeni , Vivien Didelot , Woojung Huh , Landen Chao , Sean Wang , Jiri Pirko , Amit Cohen , Christian Marangi , Hauke Mehrtens , Hans Schultz , Roopa Prabhu , DENG Qingfang , Claudiu Manoil , linux-mediatek@lists.infradead.org, Matthias Brugger , Yuwei Wang , Petr Machata , netdev@vger.kernel.org, linux-kernel@vger.kernel.org, UNGLinuxDriver@microchip.com, Vladimir Oltean , davem@davemloft.net On Sun, 23 Oct 2022 07:32:02 +0200 netdev@kapio-technology.com wrote: > >> @@ -1140,7 +1148,7 @@ static int __br_fdb_add(struct ndmsg *ndm, > >> struct net_bridge *br, > >> err = br_fdb_external_learn_add(br, p, addr, vid, true); > >> } else { > >> spin_lock_bh(&br->hash_lock); > >> - err = fdb_add_entry(br, p, addr, ndm, nlh_flags, vid, nfea_tb); > >> + err = fdb_add_entry(br, p, addr, ndm, nlh_flags, vid, ext_flags, > >> nfea_tb); > > > > I believe the preference is to wrap to 80 columns when possible. > > Very strange... since I ran checkpatch.pl from the net-next kernel > itself and it did not > give me any warnings about 80 columns, but rather said 'patch is ready > for submission'. > > As this is silent, could it be some missing python plugins or something > to do with perl? I run: ./scripts/checkpatch.pl --strict --max-line-length=80