From: Andrew Lunn <andrew.lunn@ascom.ch>
To: The list for a Better Approach To Mobile Ad-hoc Networking
<b.a.t.m.a.n@lists.open-mesh.net>
Subject: [B.A.T.M.A.N.] [batman-adv]: move vis_format from vis.c to proc.c
Date: Thu, 16 Jul 2009 09:44:01 +0200 [thread overview]
Message-ID: <20090716074401.GT19071@ma.tech.ascom.ch> (raw)
vis_format is currently in vis.c however this variable is only used in
proc.c. Move it into proc, and remove the volatile, which should not
be needed.
Signed-off-by: Andrew Lunn <andrew.lunn@ascom.ch>
Index: vis.c
===================================================================
--- vis.c (revision 1345)
+++ vis.c (working copy)
@@ -42,7 +42,6 @@
void free_info(void *data);
void send_vis_packet(struct vis_info *info);
void start_vis_timer(void);
-volatile uint8_t vis_format = DOT_DRAW;
int vis_info_cmp(void *data1, void *data2) {
Index: vis.h
===================================================================
--- vis.h (revision 1345)
+++ vis.h (working copy)
@@ -51,7 +51,6 @@
extern struct hashtable_t *vis_hash;
extern spinlock_t vis_hash_lock;
-extern volatile uint8_t vis_format;
void receive_vis_packet(struct ethhdr *ethhdr, struct vis_packet *vis_packet, int vis_info_len);
void vis_set_mode(int mode);
Index: proc.c
===================================================================
--- proc.c (revision 1345)
+++ proc.c (working copy)
@@ -31,6 +31,7 @@
#include "types.h"
#include "hash.h"
+static uint8_t vis_format = DOT_DRAW;
static struct proc_dir_entry *proc_batman_dir = NULL, *proc_interface_file = NULL, *proc_orig_interval_file = NULL, *proc_originators_file = NULL;
reply other threads:[~2009-07-16 7:44 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20090716074401.GT19071@ma.tech.ascom.ch \
--to=andrew.lunn@ascom.ch \
--cc=b.a.t.m.a.n@lists.open-mesh.net \
/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).