b.a.t.m.a.n.lists.open-mesh.org archive mirror
 help / color / mirror / Atom feed
From: Sven Eckelmann <sven@narfation.org>
To: b.a.t.m.a.n@lists.open-mesh.org
Subject: [PATCH 0/3] batman-adv: Drop ununused functions and localize when possible
Date: Wed, 02 Aug 2023 12:00:21 +0200	[thread overview]
Message-ID: <20230802-cleanup_functions-v1-0-1f9bfb914696@narfation.org> (raw)

There were a couple of functions which were still compiled but not used
anymore since a while. Just drop them and make sure that other ones are
local only (to make it easier to spot them in the future).

Signed-off-by: Sven Eckelmann <sven@narfation.org>
---
Sven Eckelmann (3):
      batman-adv: Drop unused function batadv_gw_bandwidth_set
      batman-adv: Keep batadv_netlink_notify_* static
      batman-adv: Drop per algo GW section class code

 net/batman-adv/bat_iv_ogm.c     |   1 +
 net/batman-adv/bat_v.c          |  23 +-----
 net/batman-adv/gateway_common.c | 162 +---------------------------------------
 net/batman-adv/gateway_common.h |   7 --
 net/batman-adv/netlink.c        |  15 ++--
 net/batman-adv/netlink.h        |   6 --
 net/batman-adv/types.h          |   7 +-
 7 files changed, 13 insertions(+), 208 deletions(-)
---
base-commit: ed12d0c16556942c4fd52af122030182c11e60ef
change-id: 20230802-cleanup_functions-2946498ebebc

Best regards,
-- 
Sven Eckelmann <sven@narfation.org>


             reply	other threads:[~2023-08-02 10:01 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-02 10:00 Sven Eckelmann [this message]
2023-08-02 10:00 ` [PATCH 1/3] batman-adv: Drop unused function batadv_gw_bandwidth_set Sven Eckelmann
2023-08-02 10:00 ` [PATCH 2/3] batman-adv: Keep batadv_netlink_notify_* static Sven Eckelmann
2023-08-02 10:00 ` [PATCH 3/3] batman-adv: Drop per algo GW section class code Sven Eckelmann

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=20230802-cleanup_functions-v1-0-1f9bfb914696@narfation.org \
    --to=sven@narfation.org \
    --cc=b.a.t.m.a.n@lists.open-mesh.org \
    /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;
as well as URLs for NNTP newsgroup(s).