From: Marek Lindner <mareklindner@neomailbox.ch>
To: b.a.t.m.a.n@lists.open-mesh.org
Subject: Re: [B.A.T.M.A.N.] [PATCHv5 2/2] batctl: adding mcast flags debugfs table
Date: Tue, 17 May 2016 17:14:47 +0800 [thread overview]
Message-ID: <1705687.XexGnDGZGl@voltaire> (raw)
In-Reply-To: <1463157342-13195-3-git-send-email-linus.luessing@c0d3.blue>
[-- Attachment #1: Type: text/plain, Size: 1085 bytes --]
On Friday, May 13, 2016 18:35:42 Linus Lüssing wrote:
> From: Linus Lüssing <linus.luessing@web.de>
>
> This patch adds an option to retrieve the per originator multicast
> flags table.
>
> Signed-off-by: Linus Lüssing <linus.luessing@web.de>
> ---
>
> Changes in v5:
> * fixed README description of mcast_flags (copy & paste error from DAT)
>
> Changes in v4:
> * rebase to current master (no conflicts)
>
> Changes in v3:
> * updated mcast_flags example in README file
>
> Changes in v2:
> * header_lines for 'mcast_flags' increased from 2 to 6
> * Example updated to more verbose, 6 lines debugfs header output
> * (kept order for the noted manpage section as it wasn't alphabetically
> orderd in the first place - instead keeping the previous "logical"
> order - 'mcast' after 'nc')
>
> README | 34 ++++++++++++++++++++++++++++++++++
> debug.c | 6 ++++++
> debug.h | 1 +
> functions.c | 1 +
> man/batctl.8 | 3 +++
> 5 files changed, 45 insertions(+)
Applied in revision 2f6b65f.
Thanks,
Marek
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
prev parent reply other threads:[~2016-05-17 9:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-13 16:35 [B.A.T.M.A.N.] [PATCHv5 1/2] batctl: adding multicast debug level Linus Lüssing
2016-05-13 16:35 ` [B.A.T.M.A.N.] [PATCH] batman-adv: Fix mcast_flags debugfs output Linus Lüssing
2016-05-17 9:24 ` Marek Lindner
2016-05-13 16:35 ` [B.A.T.M.A.N.] [PATCHv5 2/2] batctl: adding mcast flags debugfs table Linus Lüssing
2016-05-17 9:14 ` Marek Lindner [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=1705687.XexGnDGZGl@voltaire \
--to=mareklindner@neomailbox.ch \
--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 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.