From: "Linus Lüssing" <linus.luessing@c0d3.blue>
To: The list for a Better Approach To Mobile Ad-hoc Networking
<b.a.t.m.a.n@lists.open-mesh.org>
Subject: Re: [B.A.T.M.A.N.] [PATCH] batman-adv: Disable CONFIG_BATMAN_ADV_DEBUGFS by default
Date: Sun, 18 Mar 2018 15:39:07 +0100 [thread overview]
Message-ID: <20180318143907.GO2681@otheros> (raw)
In-Reply-To: <20180318093429.18752-1-sven@narfation.org>
On Sun, Mar 18, 2018 at 10:34:29AM +0100, Sven Eckelmann wrote:
> All tools which were known to the batman-adv development team are
> supporting the batman-adv netlink interface since a while. Also debugfs is
> not supported for batman-adv interfaces in any non-default netns. Thus
> disabling CONFIG_BATMAN_ADV_DEBUGFS by default should not cause problems on
> most systems. It is still possible to enable it in case it is still
> required in a specific setup.
I'm wondering, could this lead to some confusion if package
maintainers of a Linux distro were upgrading the kernel before
upgrading batctl?
Since this patch is not urgent, would it make sentence to delay
this patch for after the next release maybe? That should give
maintainers at least a two months window to upgrade batctl.
And should avoid users being confused of "batctl dc" or
"batctl mf" not working with the batman-adv version their
distro might already ship.
Cheers, Linus
next prev parent reply other threads:[~2018-03-18 14:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-18 9:34 [B.A.T.M.A.N.] [PATCH] batman-adv: Disable CONFIG_BATMAN_ADV_DEBUGFS by default Sven Eckelmann
2018-03-18 14:39 ` Linus Lüssing [this message]
2018-03-18 18:48 ` Sven Eckelmann
2018-04-25 17:17 ` Sven Eckelmann
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=20180318143907.GO2681@otheros \
--to=linus.luessing@c0d3.blue \
--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