public inbox for b.a.t.m.a.n@lists.open-mesh.org
 help / color / mirror / Atom feed
From: "Linus Lüssing" <linus.luessing@web.de>
To: b.a.t.m.a.n@lists.open-mesh.net
Subject: Re: [B.A.T.M.A.N.] [PATCH] batman-adv: atomic variable for vis-srv activation
Date: Wed, 13 Jan 2010 02:30:37 +0100	[thread overview]
Message-ID: <20100113013037.GA10176@Sellars> (raw)
In-Reply-To: <1263185876-24214-1-git-send-email-linus.luessing@web.de>

I now decided to use a more general variable name and as Marek
suggested the checks against the given define-values. This should
keep the structure of several "vis-modes" in general, as it had
been done before by Simon, instead of just "on" and "off".

The checkpatch-script from the batman-adv linux git branch showed
me 0 errors/warnings for this one.

- So far, just had the time to test this patch with my laptop and
  home-server only. But switching as well as receiving/displaying
  the vis-stuff worked fine for those (didn't have a closer look
  with tcpdump/wireshark for this vis-type part though).

Cheers, Linus

  reply	other threads:[~2010-01-13  1:30 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-31  3:37 [B.A.T.M.A.N.] [PATCH 1/3] batman-adv: atomic variable for vis-srv activation =?UTF-8?q?Linus=20L=C3=BCssing?=
2010-01-02 19:26 ` Marek Lindner
2010-01-05  4:20   ` Linus Lüssing
2010-01-05  7:41     ` Andrew Lunn
2010-01-07  5:23     ` Marek Lindner
2010-01-11  4:57 ` [B.A.T.M.A.N.] [PATCH] " Linus Lüssing
2010-01-13  1:30   ` Linus Lüssing [this message]
     [not found]   ` <201001151124.25877.lindner_marek@yahoo.de>
2010-01-15 18:34     ` Sven Eckelmann
2010-01-15 18:39       ` Sven Eckelmann
2010-01-15 18:50       ` Andrew Lunn
2010-01-18 20:42       ` Linus Lüssing
2010-01-20  2:02         ` Marek Lindner

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=20100113013037.GA10176@Sellars \
    --to=linus.luessing@web.de \
    --cc=b.a.t.m.a.n@lists.open-mesh.net \
    --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