Re: [PATCH net-next 00/15] pull request for net-next: batman-adv 2026-07-28
Sven Eckelmann <[email protected]> Tue, 04 Aug 2026 08:55:51 +0200
| Newsgroups | org.open-mesh.lists.batman,org.kernel.vger.netdev |
|---|---|
| Message-ID | <3386526.aV6nBDHxoP@sven-l14> |
--nextPart3093944.VdNmn5OnKV Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="utf-8"; protected-headers="v1" From: Sven Eckelmann <[email protected]> Date: Tue, 04 Aug 2026 08:55:51 +0200 Message-ID: <3386526.aV6nBDHxoP@sven-l14> In-Reply-To: <[email protected]> MIME-Version: 1.0 On Tuesday, 4 August 2026 04:19:20 CEST Jakub Kicinski wrote: > On Tue, 28 Jul 2026 15:39:03 +0200 Simon Wunderlich wrote: > > here is a minor bugfix/cleanup pull request of batman-adv to go into net-next. > > Can you look thru the Sashiko comments here (especially Medium+ > severity)? > > https://netdev-ai.bots.linux.dev/sashiko/#/patchset/[email protected] https://patchwork.open-mesh.org/bundle/ecsv/pu-main/ We were just waiting for a verdict. I am guessing it it a "no, will not merge", correct? > At a glance patch 14 does not inspire confidence. I guess patch 15 > removes the worst part - but is there a real reason not to use locking? In its current state, you would need spinlocks over larger (op-count) portions of code in the hot-path. And since it it nearly impossible to get feedback from the TT author/maintainer, I am not willing to invest time in a total rewrite of the TT infrastructure. Regards, Sven --nextPart3093944.VdNmn5OnKV Content-Type: application/pgp-signature; name="signature.asc" Content-Description: This is a digitally signed message part. Content-Transfer-Encoding: 7Bit -----BEGIN PGP SIGNATURE----- iHUEABYKAB0WIQS81G/PswftH/OW8cVND3cr0xT1ywUCanGM9wAKCRBND3cr0xT1 y3sqAP93VUsjB/3zBZEPOEwVl9F8KchEpqol2vmkE2mbdlui4gD/ZcZ0qOW3IWsP +5olqy4xUDXtdwWKz+2KDX80Fe+2mwI= =12G3 -----END PGP SIGNATURE----- --nextPart3093944.VdNmn5OnKV--