public inbox for b.a.t.m.a.n@lists.open-mesh.org
 help / color / mirror / Atom feed
From: Simon Wunderlich <sw@simonwunderlich.de>
To: b.a.t.m.a.n@lists.open-mesh.org
Subject: Re: [B.A.T.M.A.N.] [PATCH v7] alfred: Check batadv interfaces via netlink
Date: Tue, 08 Nov 2016 17:21:31 +0100	[thread overview]
Message-ID: <2171693.eEIDLaHTPd@prime> (raw)
In-Reply-To: <20161106093738.17010-1-sven@narfation.org>

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

On Sunday, November 6, 2016 10:37:38 AM CET Sven Eckelmann wrote:
> From: Jean-Jacques Sarton <jj.sarton@t-online.de>
> 
> alfred is checking the status of the mesh interface before it starts. The
> mesh interface has to have accessible debugfs files "transtable_global" and
> "originators" before alfred will accept it.
> 
> batman-adv will not create debugfs entries for network namespaces. Thus
> this check has to be modified to first check via netlink if the interface
> is providing the same information without debugfs. If it does then no check
> for the debugfs files is necessary anymore.
> 
> Signed-off-by: Jean-Jacques Sarton <jj.sarton@t-online.de>
> [sven@narfation.org: fixed commit message, mark debugfs function static,
>  fix whitespaces, fix unused init of variable, only fallback to debugfs on
>  EOPNOTSUPP, rewritten batadv_interface_check_netlink, fix return of
>  batadv_interface_check]
> Signed-off-by: Sven Eckelmann <sven@narfation.org>

Applied in 2310c47.

Thanks!
     Simon

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

      reply	other threads:[~2016-11-08 16:21 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-06  9:37 [B.A.T.M.A.N.] [PATCH v7] alfred: Check batadv interfaces via netlink Sven Eckelmann
2016-11-08 16:21 ` Simon Wunderlich [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=2171693.eEIDLaHTPd@prime \
    --to=sw@simonwunderlich.de \
    --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