From: Sven Eckelmann <sven@narfation.org>
To: b.a.t.m.a.n@lists.open-mesh.org
Subject: Re: [B.A.T.M.A.N.] [PATCHv2] batctl: Use netlink to replace some of debugfs
Date: Tue, 03 May 2016 11:47:37 +0200 [thread overview]
Message-ID: <2159279.DU25yn4Ghe@bentobox> (raw)
In-Reply-To: <1462222618-29761-1-git-send-email-andrew@lunn.ch>
[-- Attachment #1: Type: text/plain, Size: 953 bytes --]
On Monday 02 May 2016 22:56:57 Andrew Lunn wrote:
> The kernel has gained support for exporting some information via
> netlink. Use this when available, rather than debugfs.
>
> If netlink is not available, or the information is not yet available
> via netlink, batctl will fall back to debugfs.
>
> Signed-off-by: Andrew Lunn <andrew@lunn.ch>
> ---
>
> v2: Verify mandatory attributes are returned by the kernel, and that
> they have the expected size.
> ---
git-am also reports some whitespace errors:
Applying: batctl: Use netlink to replace some of debugfs
.git/rebase-apply/patch:1042: space before tab in indent.
printf("%02x:%02x:%02x:%02x:%02x:%02x ",
.git/rebase-apply/patch:1117: space before tab in indent.
printf("%02x:%02x:%02x:%02x:%02x:%02x ",
.git/rebase-apply/patch:1264: new blank line at EOF.
+
And could you please use b.a.t.m.a.n@lists.open-mesh.org to submit patches.
Kind regards,
Sven
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2016-05-03 9:47 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-02 20:56 [B.A.T.M.A.N.] [PATCHv2] batctl: Use netlink to replace some of debugfs Andrew Lunn
2016-05-03 7:07 ` Sven Eckelmann
2016-05-03 12:20 ` Andrew Lunn
2016-05-03 12:26 ` Sven Eckelmann
2016-05-03 12:47 ` Andrew Lunn
2016-05-03 12:54 ` Sven Eckelmann
2016-05-03 13:08 ` Andrew Lunn
2016-05-03 20:16 ` Marek Lindner
2016-05-03 20:30 ` Andrew Lunn
2016-05-03 9:47 ` Sven Eckelmann [this message]
2016-05-03 9:51 ` Sven Eckelmann
2016-05-03 10:30 ` Sven Eckelmann
2016-05-03 12:45 ` Andrew Lunn
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=2159279.DU25yn4Ghe@bentobox \
--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