All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sven Eckelmann <sven@narfation.org>
To: sashiko@lists.linux.dev
Cc: sw@simonwunderlich.de
Subject: Re: [PATCH batadv-next] batman-adv: use neigh_node's orig_node only as id
Date: Wed, 06 May 2026 09:10:32 +0200	[thread overview]
Message-ID: <11781550.T7Z3S40VBb@ripper> (raw)
In-Reply-To: <20260506035812.39119C2BCB8@smtp.kernel.org>

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

On Wednesday, 6 May 2026 05:58:11 CEST sashiko-bot@kernel.org wrote:
> > The orig_node member of struct batadv_neigh_node is no longer used in
> > B.A.T.M.A.N. IV. But batadv_neigh_node_create() is still storing it.
> 
> Is this description accurate? Looking at B.A.T.M.A.N. IV, the orig_node field
> still appears to be referenced in net/batman-adv/bat_iv_ogm.c in functions
> like batadv_iv_ogm_neigh_new() and batadv_iv_ogm_calc_tq().

According to the patch description, following patch needs to be applied before 
adding this changes:

prerequisite-patch-id: 8d01950de12c8f4715e9f4723a0b6f1c349e6a84

You can find the patch at 
https://lore.kernel.org/batman/?q=patchid:8d01950de12c8f4715e9f4723a0b6f1c349e6a84

And in this patch ("batman-adv: stop caching unowned originator pointers in 
BAT IV") removes the B.A.T.M.A.N. IV part.

Regards,
	Sven

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

      parent reply	other threads:[~2026-05-06  7:10 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-04 19:32 [PATCH batadv-next] batman-adv: use neigh_node's orig_node only as id Sven Eckelmann
     [not found] ` <20260506035812.39119C2BCB8@smtp.kernel.org>
2026-05-06  7:10   ` 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=11781550.T7Z3S40VBb@ripper \
    --to=sven@narfation.org \
    --cc=sashiko@lists.linux.dev \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.