From: Andrew Lunn <andrew@lunn.ch>
To: Marek Lindner <lindner_marek@yahoo.de>
Cc: b.a.t.m.a.n@lists.open-mesh.org
Subject: Re: [B.A.T.M.A.N.] [PATCH 1/2] batman-adv: add routing debug log accessible via debugfs
Date: Wed, 23 Jun 2010 17:12:33 +0200 [thread overview]
Message-ID: <20100623151233.GK15420@lunn.ch> (raw)
In-Reply-To: <201006231702.37242.lindner_marek@yahoo.de>
On Wed, Jun 23, 2010 at 05:02:36PM +0200, Marek Lindner wrote:
> On Wednesday 23 June 2010 16:51:54 Andrew Lunn wrote:
> > > +
> > > +#ifdef CONFIG_BATMAN_ADV_DEBUG
> > > +extern int debug;
> >
> > What is debug used for now? Does it still have a purpose?
>
> Oh yes, it does. You have to use it to configure the log level as before.
So you get one global setting, which affects all meshes? Should this
maybe pushed into priv? Is there a use case for having different
logging levels for different meshes in a node?
Andrew
next prev parent reply other threads:[~2010-06-23 15:12 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-23 14:20 [B.A.T.M.A.N.] batman-adv debug logging Marek Lindner
2010-06-23 14:20 ` [B.A.T.M.A.N.] [PATCH 1/2] batman-adv: add routing debug log accessible via debugfs Marek Lindner
2010-06-23 14:51 ` Andrew Lunn
2010-06-23 15:02 ` Marek Lindner
2010-06-23 15:12 ` Andrew Lunn [this message]
2010-06-23 15:53 ` Marek Lindner
2010-06-23 15:09 ` Andrew Lunn
2010-06-23 15:58 ` Marek Lindner
2010-06-23 16:12 ` Andrew Lunn
2010-06-23 15:17 ` Sven Eckelmann
2010-06-23 16:00 ` Marek Lindner
2010-06-23 15:23 ` Andrew Lunn
2010-06-23 16:03 ` Marek Lindner
2010-06-23 16:18 ` Andrew Lunn
2010-06-23 14:20 ` [B.A.T.M.A.N.] [PATCH 2/2] batctl: add debug log support Marek Lindner
-- strict thread matches above, loose matches on Subject: below --
2010-06-27 0:32 [B.A.T.M.A.N.] batman-adv debug logging (v2) Marek Lindner
2010-06-27 0:33 ` [B.A.T.M.A.N.] [PATCH 1/2] batman-adv: add routing debug log accessible via debugfs Marek Lindner
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=20100623151233.GK15420@lunn.ch \
--to=andrew@lunn.ch \
--cc=b.a.t.m.a.n@lists.open-mesh.org \
--cc=lindner_marek@yahoo.de \
/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