From: Sven Eckelmann <sven@narfation.org>
To: b.a.t.m.a.n@lists.open-mesh.org
Subject: [B.A.T.M.A.N.] [PATCH 0/5] batman-adv: Tracing and debugfs deprecation cleanups
Date: Sun, 21 Oct 2018 11:30:27 +0200 [thread overview]
Message-ID: <20181021093032.19928-1-sven@narfation.org> (raw)
Hi,
the current master branch already contains support to store debug messages
to the tracing buffer and to inform users about the deprecation of the
debugfs functionality.
This patchset is now cleaning it up a little bit more and allows to the
tracing infrastructure completely without BATMAN_ADV_DEBUGFS.
Kind regards,
Sven
Sven Eckelmann (5):
batman-adv: Drop unused lockdep include
batman-adv: Add includes for deprecation warning
batman-adv: Improve includes for trace functionality
batman-adv: Allow to use BATMAN_ADV_DEBUG without BATMAN_ADV_DEBUGFS
batman-adv: Fix description for BATMAN_ADV_DEBUG
compat.h | 5 ----
net/batman-adv/Kconfig | 7 +++--
net/batman-adv/bat_iv_ogm.c | 1 -
net/batman-adv/debugfs.c | 2 ++
net/batman-adv/log.c | 60 ++++++++++++++++++++-----------------
net/batman-adv/trace.c | 2 --
net/batman-adv/trace.h | 6 ++++
7 files changed, 45 insertions(+), 38 deletions(-)
--
2.19.1
next reply other threads:[~2018-10-21 9:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-21 9:30 Sven Eckelmann [this message]
2018-10-21 9:30 ` [B.A.T.M.A.N.] [PATCH 1/5] batman-adv: Drop unused lockdep include Sven Eckelmann
2018-10-21 9:30 ` [B.A.T.M.A.N.] [PATCH 2/5] batman-adv: Add includes for deprecation warning Sven Eckelmann
2018-10-21 9:30 ` [B.A.T.M.A.N.] [PATCH 3/5] batman-adv: Improve includes for trace functionality Sven Eckelmann
2018-10-21 9:30 ` [B.A.T.M.A.N.] [PATCH 4/5] batman-adv: Allow to use BATMAN_ADV_DEBUG without BATMAN_ADV_DEBUGFS Sven Eckelmann
2018-10-21 9:30 ` [B.A.T.M.A.N.] [PATCH 5/5] batman-adv: Fix description for BATMAN_ADV_DEBUG 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=20181021093032.19928-1-sven@narfation.org \
--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;
as well as URLs for NNTP newsgroup(s).