B.A.T.M.A.N Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Sven Eckelmann <sven@narfation.org>
To: b.a.t.m.a.n@lists.open-mesh.org,
	Remi Pommarel <repk@triplefau.lt>,
	Antonio Quartulli <a@unstable.cc>
Cc: Marek Lindner <mareklindner@neomailbox.ch>,
	Simon Wunderlich <sw@simonwunderlich.de>
Subject: Re: [PATCH v2 0/5] batman-adv: TT change events fixes and improvements
Date: Sun, 17 Nov 2024 09:24:50 +0100	[thread overview]
Message-ID: <2376061.n0HT0TaD9V@sven-l14> (raw)
In-Reply-To: <cover.1731792497.git.repk@triplefau.lt>

[-- Attachment #1: Type: text/plain, Size: 782 bytes --]

On Saturday, 16 November 2024 22:32:04 CET Remi Pommarel wrote:
> The first three patches are actual fixes.
[...]
> The next two patches are more cleanup / potential slight improvements.
> While patch 4 is mainly cosmetic (having negative tt.local_changes
> values is not exactly an issue), patch 5 is here to keep the TT changes
> list as short as possible (reducing network overhead).

Thanks for your patches. They look plausible but I want to get Acks from 
Antonio before applying them.

Minor thing (3. patch): emtpy -> empty, "a creatind" -> creating, ...


@Simon, we need to apply the first three patches to net and send them early - 
just to make sure it is merged in net-next before we send the last two 
patches. Just to avoid some merge conflicts.

Kind regards,
	Sven

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

      parent reply	other threads:[~2024-11-17  8:25 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-16 21:32 [PATCH v2 0/5] batman-adv: TT change events fixes and improvements Remi Pommarel
2024-11-16 21:32 ` [PATCH v2 1/5] batman-adv: Do not send uninitialized TT changes Remi Pommarel
2024-11-16 21:32 ` [PATCH v2 2/5] batman-adv: Remove uninitialized data in full table TT response Remi Pommarel
2024-11-16 21:32 ` [PATCH v2 3/5] batman-adv: Do not let TT changes list grows indefinitely Remi Pommarel
2024-11-16 21:32 ` [PATCH v2 4/5] batman-adv: Remove atomic usage for tt.local_changes Remi Pommarel
2024-11-16 21:32 ` [PATCH v2 5/5] batman-adv: Don't keep redundant TT change events Remi Pommarel
2024-11-17  8:25   ` Sven Eckelmann
2024-11-17  8:24 ` Sven Eckelmann [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=2376061.n0HT0TaD9V@sven-l14 \
    --to=sven@narfation.org \
    --cc=a@unstable.cc \
    --cc=b.a.t.m.a.n@lists.open-mesh.org \
    --cc=mareklindner@neomailbox.ch \
    --cc=repk@triplefau.lt \
    --cc=sw@simonwunderlich.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox